Permalink
Show file tree
Hide file tree
5 comments
on commit
sign in to comment.
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
More explicitly define font resets on form controls (#607)
- Loading branch information
Jonathan Neal
committed
Aug 8, 2016
1 parent
db6567c
commit 5d728b83a5ee6ee3e9e3158a28d6369718014e0c
Showing
3 changed files
with
8 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5d728b8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I ask what the reason behind the more explicit font definitions is? Thing is, that I usually set a base
font-family,font-sizeandline-heighton thebodytag, which usually do apply to input elements as well. This leads to me basically just adding the old rule back into my styles, overriding the one set here again which does not make too much sense in my mind. That is why I would be grateful to understand the reasoning behind this decision.5d728b8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rafhun See #591 and #607
5d728b8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
font-familyshould stayinheritIMO.5d728b8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, the
inputfont-familyshould beinherit.Since its set to
sans-serifonhtmlanyway (#591 (comment)), wouldn't usingfont-family: inheritoninputjust inherit thefont-family: sans-seriffrom thehtmlwhile still allowing the user to override it by just specifying afont-familyonhtmlorbodyand not having to explicitly specify thefont-familyforinput?5d728b8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rafhun, @jovilog, @MethodGrab, as @Florian-R pointed out, you can see the reasons behind this decision on #591 and #607. If you consider that we should reconsider this, please, open an issue or comment in the original issues, so we can track this. Comments on commits are hard to track. Thanks!