commit | 6ea2a2e7f3ef01e0c98424ce272a732ade92ad1a | [log] [tgz] |
---|---|---|
author | Javier Fernandez <jfernandez@igalia.com> | Tue Jul 17 10:01:57 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jul 17 10:01:57 2018 |
tree | b3e004dc894de0d59aad63fe48fa46c133cf3ff7 | |
parent | fe5239c6c5e393d437074e66311af0199d18135e [diff] |
[css-text] A leading white-space should break before handling overflow Leading white-spaces are indeed breaking opportunities that should prevent, if there are no other css properties forcing it, breaking text in the middle of a word when honoring the word-wrap/overflow-wrap CSS property. We are doing so if the leading white-space sequence is longer than 1 character, but when we have a single leading white-space, we are missing that breaking opportunity and we may lead to cases, like the one described in the bug. However, this breaking opportunity should be considered together with other provided by the word-break CSS property (eg, break-word or break-all). There is a discussion [1] in the CSS WG github about this issue, which provides an interoperability analysis of a few cases where a single leading white-space character may produce different results, depending on the browser and the combination of line-breaking properties. [1] https://github.com/w3c/csswg-drafts/issues/2907 Bug: 854624 Change-Id: I49ec8282e899a32990662c104b48cab04057b909 Reviewed-on: https://chromium-review.googlesource.com/1130515 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#575596}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .