Bug 119369
| Summary: | Initial value of @font-face's font-variant property should be 'normal' | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, bdakin, bfulgham, cdumez, dino, enrica, eoconnor, kling, koivisto, mitz, mmaxfield, simon.fraser, vitor.roriz, webkit-bug-importer, zalan |
| Priority: | P2 | Keywords: | BlinkMergeCandidate, InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ryosuke Niwa
Consider merging https://chromium.googlesource.com/chromium/blink/+/2987a226f418c77ec14d5aba57b2393a470b3cc3
When @font-face does not have a font-variant property, it was defaulted to
'normal,small-caps' (all supported variants). The spec says the initial
value is 'normal'.
spec: http://www.w3.org/TR/css3-fonts/#propdef-font-variant
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
I am able to reproduce this bug in Safari 15.6.1 and Safari Technology Preview 151, I took the test case from Chromium commit and changed the URL for the Ahem font to Hixie Resources.
Link - https://jsfiddle.net/91jg0238/show
*** Safari 15.6.1 on macOS 12.5.1 ***
Text - Failrue
*** Safari Technology Preview 151 ***
Text - Failrue
*** Chrome Canary 106 ***
Black bars over "Failure text" space as per expected results
*** Firefox Nightly 105 ***
Black bars over "Failure text" space as per expected results
____________
Just wanted to share updated test results. Thanks!
Radar WebKit Bug Importer
<rdar://problem/98934841>
Ahmad Saleem
This commit removed the code, which can enable this to be merged into Webkit:
https://github.com/WebKit/WebKit/commit/a46177f3176e2ad4f223505ac9c167b4a73fe7dc
I don't think it would be easy to merge and fix this just by replacing the small bit now.
Ryosuke Niwa
This is Later at this point. Our codebase has diverged quite a bit
Alexey Proskuryakov
We are passing the test that was added with the Chromium commit when it's executed from LayoutTests/fast/css -> config changed.
I didn't look into what's up with the failing JSFiddle deeply; maybe it's refusing to load Ahem due to insecure content blocking (http subresource in a https document).