Re: [w3c/editing] Should contenteditable have break-word behavior by default? (#145)

Oddly enough, this has been fixed for Android scenarios only. Can we agree that this is the behavior that we want and proceed with fixing it on Chrome desktop so Chrome can have consistent behavior with itself?
Here are Android release [notes ](https://blog.chromium.org/2017/02/chrome-57-beta-css-grid-layout-improved.html)from last year.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/145#issuecomment-432762468

Received on Wednesday, 24 October 2018 17:52:53 UTC