Furigana don’t affect element height/layout, and the container hides overflow. For example:
Changing style on
.topic-body .cooked to be
overflow: visible fixes this, though that might also let intentional/annoying overflows through.
This is on latest Firefox (83.0b6) on macOS. Cannot reproduce on Chrome (67).
Thanks for reporting this!
I think we can convert the
margin-top: 15px from
.regular.contents to be
padding-top: 15px on
.cooked instead… that would allow us to keep the same spacing and hide overflow, but allows 15px of additional overflow on top (which should be plenty of space for Furigana)…
I need to check to make sure the switch doesn’t cause other issues, but I don’t see any obvious roadblocks…
This has been merged, you can see it in action with this example: 漢字
This topic was automatically closed after 5 days. New replies are no longer allowed.