REOPENED 168258
"font-family: initial" works differently for form elements compared to regular ones
https://bugs.webkit.org/show_bug.cgi?id=168258
Summary "font-family: initial" works differently for form elements compared to regula...
Vladimir Starkov
Reported 2017-02-13 15:00:25 PST
DEMO http://dabblet.com/gist/6fc61a20d75183bcd346f34fa96630f2 Steps to reproduce: HTML: <a class="btn">Button</a> <button class="btn">Button</a> CSS: /* all initial works differently for links and buttons */ .btn { all: initial; background: red; } Actual results: Button and Link look differently from each other (font-family, bottom and top borders dont match) Expected results: Should look the same
Attachments
expected (10.62 KB, image/png)
2017-02-13 15:01 PST, Vladimir Starkov
no flags
actual (11.12 KB, image/png)
2017-02-13 15:02 PST, Vladimir Starkov
no flags
Example to reproduce the issue (321 bytes, text/html)
2017-04-18 05:08 PDT, Manuel Rego Casasnovas
no flags
Vladimir Starkov
Comment 1 2017-02-13 15:01:51 PST
Created attachment 301397 [details] expected
Vladimir Starkov
Comment 2 2017-02-13 15:02:24 PST
Radar WebKit Bug Importer
Comment 3 2017-02-15 09:11:54 PST
Manuel Rego Casasnovas
Comment 4 2017-04-18 05:08:15 PDT
Created attachment 307374 [details] Example to reproduce the issue This happens with all the "form elements" like inputs and that kind of things. It's enough with using "font-family: initial" to reproduce the issue. In the attached example on my Linux machine I got: div: -webkit-standard input: Cantarell On a macpro: div: -webkit-standard input: -apple-system While in Chrome and Firefox both elements have the same value.
Myles C. Maxfield
Comment 5 2017-04-25 14:21:02 PDT
Buttons have their initial font family set to the system font. This isn't a bug.
Myles C. Maxfield
Comment 6 2017-04-25 14:22:38 PDT
I guess there's a compat problem if the other browsers do it.
Manuel Rego Casasnovas
Comment 7 2017-05-04 07:27:20 PDT
(In reply to Myles C. Maxfield from comment #6) > I guess there's a compat problem if the other browsers do it. Should we follow up with the CSS WG or not? I can report an issue on GitHub if you think it's the way to go.
Ahmad Saleem
Comment 8 2022-10-16 06:01:18 PDT
All browsers differ in the attached test case example: *** Chrome Canary 108 *** div: Times input: Times *** Firefox Nightly 107 *** div: serif input: serif *** Safari Technology Preview 155 on macOS 12.6 *** div: -webkit-standard input: -webkit-standard _____ Just wanted to share updated results. Thanks!
Note You need to log in before you can comment on or make changes to this bug.