New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 884742 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Feature



Sign in to add a comment

Update default typography on html.css

Project Member Reported by hwi@chromium.org, Sep 17

Issue description

Motivation: 

When the default typography is more legible by default, individual web pages don't need to add own CSS to fix the default style.

And also, for the cases like text.npr.org, where intentionally not adding css to make its page loading as fast as possible especially in slow/unstable connection, updated legibility is a great help because better legibility allows *faster* recognition and consumption of critical information.

Orignial context: 
https://twitter.com/mwichary/status/1040765825467146240

html.css:
https://codesearch.chromium.org/chromium/src/third_party/blink/renderer/core/css/html.css?rcl=9a4a94d66c8b42c979b083a4062ea1b696b146e8&l=57

I'm looking for someone who knows about potential implications of changes to html.css, and can collaborate to find ways to improve the experience. I'm happy to coordinate on the design side. 

Thanks in advance!

 
Screenshot_20180917-083720.png
318 KB View Download
Cc: noyau@chromium.org
Owner: mrsuyi@chromium.org
Status: Assigned (was: Untriaged)
Not sure if you are looking for an iOS solution or a blink solution.
c#1:
Hi kariahda@, I'm looking for a blink solution. The crbug automatically added "ios-bug" when I selected the all OS checkboxes. Thanks!
If this is a bug for blink, should we reassign this to blink team?
Status: Untriaged (was: Assigned)
Cc: mrsuyi@chromium.org
Labels: -OS-iOS
Owner: ----
This is not about iOS, is it?
Status: WontFix (was: Untriaged)
Any significant change to the defaults will require spec changes and will have interop and site compat issues. We could change how we render pure text content (i.e. served as text/plain) but that won't help here. There is also the issue around respect the users preferences and accessibility settings.

If this is something you're passionate about I suggest you bring it up with the CSS working group as this isn't somehting we can change unilaterally.

Sign in to add a comment