- From: Taylor Hunt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Dec 2019 14:22:11 +0000
- To: public-css-archive@w3.org
That seems like a better solution to me. The two-value syntax seems cleaner, but I'm not sure all permutations would result in useful behavior. On Mon, Dec 16, 2019, 4:56 AM Florian Rivoal <notifications@github.com> wrote: > My feeling that that if we accept this, it should be a value of > overflow-wrap (overflow-wrap: hyphenate or overflow-wrap: hyphens) rather > than a new value of hyphens. It would do nothing if there is no risk of > overflow, hyphenate the same way hyphens:auto does but only in cases of > things would otherwise overflow, and do the same as overflow-wrap: > anywhere if hyphenation was not applicable to the word (or wasn't enough > to remove overflow). Or possibly, overflow-wrap could take hyphenate plus > another keyword from anywhere | break-word | normal to let authors chose > what to do if hyphenation doesn't solve the overflow problem. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/csswg-drafts/issues/4600?email_source=notifications&email_token=AB5S2ST7R4IPIEY3M6YSGIDQY5GDTA5CNFSM4J2X4BDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG6EVCQ#issuecomment-565987978>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB5S2SULXPPHKOGYAOXSECTQY5GDTANCNFSM4J2X4BDA> > . > -- GitHub Notification of comment by tigt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4600#issuecomment-566082015 using your GitHub account
Received on Monday, 16 December 2019 14:22:13 UTC