Summary: | CSS hyphens: auto should not work if lang="" is not declared | ||
---|---|---|---|
Product: | WebKit | Reporter: | Simon Pieters (:zcorpan) <zcorpan> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | 7raivis, ap, bfulgham, mmaxfield, simon.fraser, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari Technology Preview | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Simon Pieters (:zcorpan)
2016-12-26 15:13:01 PST
This makes sense in principle, as system language doesn't necessarily match content language. But there are quite a few features that default to system language. From the top of my head: default fonts and font fallback; quotes; spellchecker language; even default character encoding. I think that preventing hyphenation when a language is not explicitly specified would be inconsistent and confusing. I think those other defaults can also be problematic, especially for users who travel and use someone else's computer (or public computer), or users who visits sites in different languages. I think there has also been some experiments to move away from using system language for at least character encoding fallback in Gecko. WebKit prevents hyphenation for lang="unknownasdfasdf", which is already inconsistent with the other features you mention. Maybe we should take this discussion to the CSSWG? I agree with Alexey. Removing hyphenation which used to "work" would be viewed by our users as a regression. Spec issue opened: https://github.com/w3c/csswg-drafts/issues/869 The spec issue has been resolved to disallow hyphenation when no language is declared. https://github.com/w3c/csswg-drafts/issues/869#issuecomment-394938653 The Chrome bug says they fixed it, but Hixie's test case still shows hyphens with No Lang on Chrome 103.0.5060.114. Firefox (I guess, correctly) does not hyphenate for No Lang. We don't seem to do very well in wpt/css/css-text/hyphens, so pulling in as a bug. |