News for hackers. Stuff that matters.
Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by true_religion on Saturday May 05, 2018 @04:17PM (#17003564)
Internet Explore, Firefox, and Edge don't support the 'break-word' value for word-break in CSS.

Only Webkit based browsers support that. If you make the mistake of testing/developing primarily in Safari + Chrome, you'll never discover the error.

They might have also used 'keep-all' which isn't supported in Edge, but is supported everywhere else, and have a fallback rule of break-all leading the behavior seen.

tl;dr:

There's actually no universal way of setting word-breaks for textarea's or pseudo-textarea, so I can't imagine if that writing a rich text input field is easy considering you have no foundations to work on.

Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by jsjohnst on Saturday May 05, 2018 @09:38PM (#17004864)
> If you make the mistake of testing/developing primarily in Safari + Chrome

If random startups can test all common browsers and ensure good experiences, I can’t see any reasonable justification why Google can’t.