RESOLVED CONFIGURATION CHANGED184085
[Simple line layout] Text at wrong position
https://bugs.webkit.org/show_bug.cgi?id=184085
Summary [Simple line layout] Text at wrong position
Tobi Reif
Reported 2018-03-28 08:14:55 PDT
(As soon as it's clear what's happening, please set the title to something more specific.) Steps: Open https://tobireif.com/demos/grid/ in Safari (or TP), click "Layout 2", make the window narrower until some of the pink text becomes rotated. Scroll down. Open eg Chrome, do the same. Flip forth and back, comparing the layouts. Observe that the word "Supported" jumps much more than the other words - it's positioned much more to the right (top-right)(east-north-east) in Safari. And the word "Quick" is too far to the right. Same result when comparing to Firefox. When I make the Safari window a bit more narrow, sometimes the two words jump into place.
Attachments
alan
Comment 1 2018-03-28 15:49:21 PDT
It seems like the combination of "text-align: center" and "letter-spacing" confuses simple line layout.
alan
Comment 2 2018-03-28 16:08:40 PDT
(In reply to Tobi Reif from comment #0) > (As soon as it's clear what's happening, please set the title to something > more specific.) > > Steps: Open https://tobireif.com/demos/grid/ in Safari (or TP), click > "Layout 2", make the window narrower until some of the pink text becomes > rotated. Scroll down. Open eg Chrome, do the same. Flip forth and back, > comparing the layouts. Observe that the word "Supported" jumps much more > than the other words - it's positioned much more to the right > (top-right)(east-north-east) in Safari. And the word "Quick" is too far to > the right. > > Same result when comparing to Firefox. > > When I make the Safari window a bit more narrow, sometimes the two words > jump into place. Tobi, could you check it with the latest night build, please? It seems to get fixed by r229867. (I can repro this with 11.1 but works fine with trunk)
Tobi Reif
Comment 3 2018-03-29 01:45:23 PDT
Tobi Reif
Comment 4 2018-04-01 02:37:21 PDT
Checked - yep, it's fixed. Thanks all!
Note You need to log in before you can comment on or make changes to this bug.