Bug 197277

Summary:

break-all+break-spaces should not break before the first space after a word if there are previous opportunities

Product:

WebKit

Reporter:

Javier Fernandez <jfernandez>

Component:

Text

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED DUPLICATE

Severity:

Normal

CC:

crzwdjk, jfernandez, mmaxfield

Priority:

Version:

Safari Technology Preview

Hardware:

Unspecified

OS:

Unspecified

See Also:

https://bugs.chromium.org/p/chromium/issues/detail?id=952254
https://bugs.webkit.org/show_bug.cgi?id=197278

Attachments:

Description	Flags
Test case to reproduce the issue	none
Actual result	none
Expected result	none
Test case to reproduce the issues related to break-all	none

Javier Fernandez

Reported 2019-04-25 03:56:43 PDT

Created attachment 368225 [details] Test case to reproduce the issue What steps will reproduce the problem? (1) Load the attached test case What is the expected result? The line is broken after the first word "XX" (see expected.png) What happens instead? The line is broken after the second word, "XX X" (see actual.png)

Attachments
Test case to reproduce the issue (251 bytes, text/html) 2019-04-25 03:56 PDT, Javier Fernandez	no flags	Details
Actual result (828 bytes, image/png) 2019-04-25 03:57 PDT, Javier Fernandez	no flags	Details
Expected result (776 bytes, image/png) 2019-04-25 03:58 PDT, Javier Fernandez	no flags	Details
Test case to reproduce the issues related to break-all (277 bytes, text/html) 2019-04-25 04:13 PDT, Javier Fernandez	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Javier Fernandez

Comment 1 2019-04-25 03:57:48 PDT

Created attachment 368226 [details] Actual result

Javier Fernandez

Comment 2 2019-04-25 03:58:13 PDT

Created attachment 368227 [details] Expected result

Javier Fernandez

Comment 3 2019-04-25 04:09:54 PDT

This issue has many angles, since previous opportunities may be just white spaces or even between letters in case of 'word-break: break-all' is being used.

Javier Fernandez

Comment 4 2019-04-25 04:13:33 PDT

Created attachment 368229 [details] Test case to reproduce the issues related to break-all

Javier Fernandez

Comment 5 2019-04-26 09:40:18 PDT

This bug is pretty related, probably a subcase, of bug #197278

Arcady Goldmints-Orlov

Comment 6 2022-01-17 09:43:51 PST

This has been fixed by r288070 allowing LFC integration to work with the complex text path. *** This bug has been marked as a duplicate of bug 235266 ***

Note You need to log in before you can comment on or make changes to this bug.