- From: Tobi Reif via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jun 2018 14:59:16 +0000
- To: public-css-archive@w3.org
Thanks for the info!
Replacing each respective text with SVG has major drawbacks: Some might fear that it might impact eg search engine visibility. Imagine a newspaper considering to use SVG for its headlines while search engines are known to handle h1/h2/etc well - they probably wouldn't take that risk. And it might also impact accessibility, see https://www.google.com/search?q=svg+text+screen+readers . It's a potential issue as far as I can see (eg in a given specific screen reader), while HTML text can be expected to just work. Also, SVG is meant for graphics( which might contain text or not) - a pure text page (eg an article) coded in HTML shouldn't have to use SVG just to get consistent cross-OS text-layout (for its large text instances).
Thus it would be great if consistent cross-OS text-layout would be available in HTML as well (not just in SVG).
Perhaps CSS could offer that same glyph-bounding-box-based layout (which browsers already have implemented for SVG) as option for (typically large) HTML text?
eg `h1 {text-layout: glyph-bounding-box}`
(the exact name could be different)
That would solve the issue completely.
--
GitHub Notification of comment by tobireif
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2228#issuecomment-398084204 using your GitHub account
Received on Monday, 18 June 2018 14:59:19 UTC