Bug 197277 - break-all+break-spaces should not break before the first space after a word if there are previous opportunities
Summary: break-all+break-spaces should not break before the first space after a word i...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-25 03:56 PDT by Javier Fernandez
Modified: 2019-04-26 09:40 PDT (History)
2 users (show)

See Also:


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

Note You need to log in before you can comment on or make changes to this bug.
Description Javier Fernandez 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)
Comment 1 Javier Fernandez 2019-04-25 03:57:48 PDT
Created attachment 368226 [details]
Actual result
Comment 2 Javier Fernandez 2019-04-25 03:58:13 PDT
Created attachment 368227 [details]
Expected result
Comment 3 Javier Fernandez 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.
Comment 4 Javier Fernandez 2019-04-25 04:13:33 PDT
Created attachment 368229 [details]
Test case to reproduce the issues related to break-all
Comment 5 Javier Fernandez 2019-04-26 09:40:18 PDT
This bug is pretty related, probably a subcase, of bug #197278