>There's no "correct" way to typeset a document They can add multiple typesetting properties and allow the develop to decide which one to use. Besides, letting

>There's no "correct" way to typeset a document They can add multiple typesetting properties and allow the develop to decide which one to use. Besides, letting each browser decide what the "best" line break looks like doesn't solve the problem of there not being a definitive answer to that question. Even here, I don't think the Chrome developers have a vastly different opinion on what a good line break looks like. It's possible they didn't like the performance implications of webkit's version or had some other tangential reason, although the blog says performance is not an issue.