- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Oct 2018 19:06:58 +0000
- To: public-css-archive@w3.org
> Still, I'm surprised that difficulty of implementation would win out over the accessibility problems of wrapping individual letters in a bunch of spans. The hierarchy of concerns tells us that certain players in the space matter more than others; user-a11y is generally more important than implementation difficulty. It is not, however, absolute - `::nth-letter()` has *significant* implementation difficulties, over and above even that of `::first-letter` which is already troublesome, *and* has less-common use-cases. All of these combine to at least make `::nth-letter()` a *rather low priority* project, versus many other things we could add to CSS. Solving the a11y issues can be done more simply than adding `::nth-letter()`, such as having something in HTML or CSS that says "this element is not a semantic separation of its contained text from the surrounding text", which could be applied to the `span`s. This would also solve slightly wider problems than `::nth-letter()`, as anything that splits up a word for any reason could also use it, rather than the solution being limited solely to the use-case of applying different CSS to letter-based groupings. > Dredge up. > > Interesting. ? I'm confused, it looks like you might be reading some deep meaning into my wording? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3208#issuecomment-429976439 using your GitHub account
Received on Monday, 15 October 2018 19:07:00 UTC