-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List item forces strict line height #38
Comments
This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e
This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e
This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304}
This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304}
This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304}
Triggering on element type (like Gecko) kind of makes more sense to me, though. |
OK, that sounds good to me. :) |
I have no idea how this stuff works, sorry. @dbaron might. |
And in particular, the behavior seems to not be quite what's described above. Here's the behavior I see on the testcase from #38 (comment) in Chrome as far as I can tell:
In Gecko, I see the following behavior:
So the Gecko behavior is falling out of an interaction between the list marker and line-height calculations, though I dunno what's going on with the " I did look and we have some code in line layout to do something special for the last line of an |
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <[email protected]> Reviewed-by: Aleks Totic <[email protected]> Reviewed-by: Koji Ishii <[email protected]> Reviewed-by: Emil A Eklund <[email protected]> Cr-Commit-Position: refs/heads/master@{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: c6a8d1fbea4cdc17fd4dd9ba4d30f5bd5c31c05e
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: e820da6c7a2e8b6a9d20eb4dc0bddf2c4e763035
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: c6a8d1fbea4cdc17fd4dd9ba4d30f5bd5c31c05e
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: e820da6c7a2e8b6a9d20eb4dc0bddf2c4e763035
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: c6a8d1fbea4cdc17fd4dd9ba4d30f5bd5c31c05e
… inside list items., a=testonly Automatic update from web-platform-tests [LayoutNG] Don't allow line height quirk inside list items. This makes us match legacy engine behavior more closely, and both Edge and Firefox have something similar, although Firefox triggers based on element type (LI), and not display type (list-item). There's currently nothing in the spec [1] that suggests such special behavior for list items. [1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk This fix makes the line height differences go away in the test tables/mozilla/bugs/bug23235.html (but note that it will still require a rebaseline, because of minor text rendering differences between legacy and NG). See whatwg/quirks#38 for spec discussion. Change-Id: I396c0c85454feeaa45a0a5953b9e6b7c475d131e Reviewed-on: https://chromium-review.googlesource.com/c/1379897 Commit-Queue: Emil A Eklund <eaechromium.org> Reviewed-by: Aleks Totic <atoticchromium.org> Reviewed-by: Koji Ishii <kojiichromium.org> Reviewed-by: Emil A Eklund <eaechromium.org> Cr-Commit-Position: refs/heads/master{#618304} -- wpt-commits: 6bfd51316130abc1d6b648ba281792fb34e4ee82 wpt-pr: 14623 UltraBlame original commit: e820da6c7a2e8b6a9d20eb4dc0bddf2c4e763035
It seems that all browsers agree that list items disable the line height quirk [1] on ALL lines. I'm guessing this was added to make sure that there always be room for the list item marker, although that doesn't really explain why it should be like this on every line in the list item. Doing it on the first line (where the list item marker is) would have been good enough.
One implementation difference: Gecko triggers on HTML LI elements, while the others trigger on CSS display:list-item
Example:
Try changing from LI to DIV and observe the changes.
[1] https://quirks.spec.whatwg.org/#the-line-height-calculation-quirk
The text was updated successfully, but these errors were encountered: