This idea sounds like overdesign to me. I think @supports should have a simple implementation as it does now. I absolutely do not think we should turn it into an ill-defined way of querying capabilities, like whatever "nice" hyphenation would be for a given language. We really should not be designing extensive hyphenation controls until we have more solid feedback about current implementations. Chrome still lacks any support for hyphenation, which is sort of baffling. But maybe work is underway. Some of the properties Dave points out would be interesting. Not really keen on word spacing, I think that's usually a crutch to work around poor hyphenation algorithms. Cheers, John
Received on Wednesday, 17 June 2015 14:34:11 UTC