Closed
Bug 1199140
Opened 9 years ago
Closed 9 years ago
Input font not inherited from body css. Shows Segoe UI instead
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1196325
People
(Reporter: fernando.ferreira, Unassigned)
Details
(Keywords: fonts, testcase)
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150812163655
Steps to reproduce:
Created a page with Arial as the body default font family.
Actual results:
Segoe UI was used for the inputs
Expected results:
Arial should have been used as it should have inherited the font family from body
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Comment 3•9 years ago
|
||
You should define a font for the input element(s) specifically rather than expecting it to be inherited.
resource://gre-resources/forms.css line 54
input { font: -moz-field; }
![]() |
||
Comment 4•9 years ago
|
||
Yep, input elements are styled by the UA stylesheet with the default textfield font for the OS. You can use "font-family: inherit" explicitly if that's the behavior you want.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 5•9 years ago
|
||
Reporter | ||
Comment 6•9 years ago
|
||
Greetings
I understand that it is possible to apply the desired behaviour by changing the CSS in the way suggested in Comment 4.
Can you verify if there was a change in behaviour from older versions of Firefox introduced somehow in Firefox 40?
Attachment 8654662 [details] is the same testcase rendered by Firefox 37 and it displays the expected behaviour (input elements shown in Arial).
The motivation of this bug report was that many pages that used to show Arial on input elements are now showing Segoe UI on Windows 7 without any change in the underlying markup or stylesheet.
Maybe it is not the fact that input font family were inherited from body on FF 39 and older and now they aren't, some other factor could have caused this change in behaviour.
![]() |
||
Comment 7•9 years ago
|
||
> Can you verify if there was a change in behaviour from older versions of Firefox
> introduced somehow in Firefox 40?
Yes, there was a behavior change in terms of what's considered the "OS default" font. See bug 1123654 and the discussion in bug 1196325.
But also see bug 1194055 which has some further changes which I _think_ might end up shipping in a dot release and change things back to more how they used to be...
Reporter | ||
Comment 8•9 years ago
|
||
Thanks. As this bug is an invalid bug (as the cause of the problem was misinterpreted) I'll continue the discussion on Bug 1196325. Thanks a lot, keep up the good work.
Reporter | ||
Comment 9•9 years ago
|
||
Changed from Invalid to Duplicated of Bug 1196325. The diagnosis was incorrect but the issue is the same described in that bug.
Resolution: INVALID → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•