| Summary: | MDN compat table "No" cell with annotations looks broken on Safari | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Tim Nguyen (:ntim) <ntim> | ||||||
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | NEW --- | ||||||||
| Severity: | Normal | CC: | webkit-bug-importer, zalan | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | Safari 14 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Tim Nguyen (:ntim)
2021-03-26 11:31:31 PDT
Created attachment 424381 [details]
testcase.html
Here's a reduced testcase.
I filed https://github.com/mdn/yari/issues/3373 and there is some activity there. It seems to be a difference in how browsers handle line-breaking after hyphens according to the last comment there. Even more minimal testcase of differing behaviour from Jonathan Kew:
data:text/html,<style>b{display:inline-block;width:1ch;}</style><b>-x-</b>
It doesn't not even need to be an inline-block element as this is simply about soft wrap opportunities and whether we consider the position after "-" as one.
<style>
div {
width:1ch;
}
</style>
<div>-should_this_be_on_the_second_line?</div>
I actually prefer the FF approach but don't have a strong preference on this -and I assume the spec is not clear on this case. |