Infer theme-color from html content |
|||||||||||||||||||||||
Issue descriptionOS: Android Specification: https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color Motivation: Supporting "theme-color" meta tag provides great user experience. But many top web sites do not provide "theme-color" in the document even though the web site has a particular theme. Only 20% (approx) of top Alexa web sites support "theme-color". We can infer "theme-color" from html content for rest of the websites whenever possible. We did an experiment with top ~200 websites, only ~40 sites has "theme-color" meta tag in document and we could infer theme-color for ~70 of the websites which do not specify "theme-color" meta tag and some of the websites had default theme as white which matches the default theme of the browser UI. As we are trying to infer based on some heuristics, this might pick up wrong theme-color sometimes. But, we could see find only 2 such cases out of 70. Compatibility Risk None Technical constraints None. Some of the top websites which we can improve 1. amazon.* 2. linkedin.com 3. dropbox.com 4. w3schools.com 5. wikihow.com 6. bestbuy.com 7. oracle.com 8. fedex.com 9. naver.com 10. daum.net Please let us know your thoughts on this.
,
Aug 21
,
Aug 21
+tedchoc@ and mdjones@ since this is toolbar related (kind of).
,
Aug 21
I'm not convinced that this is something we should implement for a couple of reasons: - In cases like linkedin, their logged-in pages do actually have a theme color specified. Maybe the choice was intentional? In that case, does chrome have a default color? It seems like we are subtly making the theme color tag a requirement rather than optional, especially if we get the color very wrong. - If done, this is something that should probably be implemented in the c++/blink side of things to maintain consistency with the other platforms (even if they may not use the color). I don't think we should restrict this to Android. - Depending on the heuristic, this could be expensive to do on lower-end devices which is definitely something we don't want.
,
Sep 3
- In cases like linkedin, their logged-in pages do actually have a theme color specified. Maybe the choice was intentional? In that case, does chrome have a default color? It seems like we are subtly making the theme color tag a requirement rather than optional, especially if we get the color very wrong. >> If the theme-color meta is not set, chrome has a default native UI color(gray). We don't know reasons of not specifying theme-color meta tag by the websites. But, theme-color makes the websites look better, more like native apps. Yes, we might infer theme color wrong sometimes but that might occur very less number of times. Please check the attached screenshots for Alexa top websites. - If done, this is something that should probably be implemented in the c++/blink side of things to maintain consistency with the other platforms (even if they may not use the color). I don't think we should restrict this to Android. >> Agree, we should implement it in the c++/blink side of things to maintain consistency with the other platforms. - Depending on the heuristic, this could be expensive to do on lower-end devices which is definitely something we don't want. >> We will execute this algorithm if the meta tag is not specified. Need to evaluate the performance on low-end devices, may be we can enable it only for high end devices depending on the results.
,
Sep 3
,
Sep 3
,
Sep 3
,
Sep 3
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chrishtr@chromium.org
, Aug 20Labels: -Type-Bug Type-Feature