8000 [css21][css-inline] behavior differences when the primary font does not contain U+0020 · Issue #1798 · w3c/csswg-drafts · GitHub
[go: up one dir, main page]
Skip to content

[css21][css-inline] behavior differences when the primary font does not contain U+0020 #1798

New issue
New issue
Closed
Closed
[css21][css-inline] behavior differences when the primary font does not contain U+0020#1798
Assignees
frivoal
Labels
CSS2Closed Accepted by CSSWG Resolutioncss-inline-3Current Work
@frivoal

Description

@frivoal
frivoal
opened on Sep 11, 2017

This is part of the #1796 series. Read that issue for context

Test source
Ref source
Live test
Live ref

If a inline-level box contains only characters from fallback fonts, we've got two different behaviors, plus a bug: * Edge and Safari: size the height of the inline-level box using the metrics of the fonts actually used **plus** the metrics of the primary font, even if it is not used. I.E. they take the strut into account. * Chrome: size the height of the inline-level box using **only** the metrics of the fonts actually used. I.E. it does not take the strut into account. * Firefox has multiple behaviors it randomly switches between. In the test linked to above, FF does the same as chrome, but if you load the Firefox Torture test linked to bellow, it will randomly exhibit multiple behaviors as you reload the page. This is clearly a bug, but does not clearly indicate what behavior is intended.

I suggest we align with Edge & Safari.

Edit: this test file is exposing more subtle things that I initially thought. See next comment for details.

Firefox torture test:
Test source
Live test

Metadata

Metadata

Assignees

Labels

CSS2Closed Accepted by CSSWG Resolutioncss-inline-3Current Work

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    0