|
Lines 1-3
a/Source/WebCore/ChangeLog_sec1
|
|
|
1 |
2019-03-07 Javier Fernandez <jfernandez@igalia.com> |
| 2 |
|
| 3 |
word is not broken, honoring word-break: break-all, if there is a single leading space and pre-wrap |
| 4 |
https://bugs.webkit.org/show_bug.cgi?id=195361 |
| 5 |
|
| 6 |
Reviewed by NOBODY (OOPS!). |
| 7 |
|
| 8 |
We must consider leading white-spaces as potential soft-breaking |
| 9 |
opportunities that may avoid breaking in the middle of the word. |
| 10 |
|
| 11 |
However, 'break-word: break-all' [1] implies that we should ignore |
| 12 |
previous opportunities and break at any character (among the ones |
| 13 |
valid for 'break-all') that prevents the line to overflow. Note, |
| 14 |
that these breakable characters are different from the ones |
| 15 |
provided by 'line-break: anywhere' [2]. |
| 16 |
|
| 17 |
No new tests; this change is covered by the already existent tests |
| 18 |
of the CSS Text 3 suite of the Web Platform Tests. |
| 19 |
|
| 20 |
The word-break-break-all-010.html was precisely designed to cover |
| 21 |
the basic issue fixed with this change, verifying that the word is |
| 22 |
indeed broken even if a single leading space constitutes a |
| 23 |
previous soft-breaking opportunity. |
| 24 |
|
| 25 |
There are other Web Platform Tests. which already pass before this |
| 26 |
change, to verify that such leading white-space must be used |
| 27 |
instead of breaking the word in any other case, including |
| 28 |
overflow-wrap: break-word and even the deprecated word-break: |
| 29 |
break-word. |
| 30 |
|
| 31 |
- white-space/pre-wrap-016.html |
| 32 |
- overflow-wrap/overflow-wrap-break-word-004.html |
| 33 |
- overflow-wrap/overflow-wrap-break-word-005.html |
| 34 |
|
| 35 |
[1] https://drafts.csswg.org/css-text-3/#valdef-word-break-break-all |
| 36 |
[2] https://drafts.csswg.org/css-text-3/#valdef-line-break-anywhere |
| 37 |
|
| 38 |
* rendering/line/BreakingContext.h: |
| 39 |
(WebCore::BreakingContext::handleText): |
| 40 |
|
| 1 |
2019-03-10 Ross Kirsling <ross.kirsling@sony.com> |
41 |
2019-03-10 Ross Kirsling <ross.kirsling@sony.com> |
| 2 |
|
42 |
|
| 3 |
Invalid flags in a RegExp literal should be an early SyntaxError |
43 |
Invalid flags in a RegExp literal should be an early SyntaxError |