RESOLVED WORKSFORME150029
Incorrect initial rendering with Tab characters and white-space:pre/padding-left
https://bugs.webkit.org/show_bug.cgi?id=150029
Summary Incorrect initial rendering with Tab characters and white-space:pre/padding-left
Adam Roben (:aroben)
Reported 2015-10-12 07:46:39 PDT
Created attachment 262887 [details] test file to demonstrate the bug Elements with padding-left and white-space:pre that contain a Tab character render differently depending on whether the element has any element children. To reproduce: 1. Open the attached tab-test.html 2. See that the two pairs of example lines are not left-aligned with each other 3. Select the text in the page Now the example lines *are* left-aligned with each other. See attached GIF for an animation demonstrating the behavior. The only difference between the lines in each pair is that one of them contains a <span> and the other does not. This affects code rendering on github.com. This particular example was reduced from https://github.com/phonyphonecall/mb-gnu-docker-mgr/blob/7a8e67de3389a3ebf8f82e2d4ceab2ccedb5d360/mb-gnu-docker-mgr.go
Attachments
test file to demonstrate the bug (906 bytes, text/html)
2015-10-12 07:46 PDT, Adam Roben (:aroben)
no flags
GIF showing the bug (383.74 KB, image/gif)
2015-10-12 07:46 PDT, Adam Roben (:aroben)
no flags
Verified on nightly (201.55 KB, image/png)
2015-10-14 08:17 PDT, alan
no flags
Adam Roben (:aroben)
Comment 1 2015-10-12 07:46:57 PDT
Created attachment 262888 [details] GIF showing the bug
Adam Roben (:aroben)
Comment 2 2015-10-12 07:48:38 PDT
I've been testing with Safari 9 on OS X 10.11. The bug does not occur in Chrome 45 or Firefox 41.
alan
Comment 3 2015-10-13 21:11:57 PDT
This works fine with r191029. It must have been fixed by one of my simple line layout patches. (when the text is selected, we switch bail out of simple line layout. Different text positions (selected vs non-selected text) is an indication of a simple line layout bug. )
Adam Roben (:aroben)
Comment 4 2015-10-14 04:57:35 PDT
Sorry for not testing in the nightly before filing this! I just tried to verify in the latest nightly build (r191040), but the bug still reproduced. But I'm actually not sure the nightly WebKit was being used (maybe due to System Integrity Protection?); navigator.userAgent didn't mention the nightly build at all. Is there something special I need to do to use nightly builds on El Capitan?
alan
Comment 5 2015-10-14 08:16:54 PDT
(In reply to comment #4) > Sorry for not testing in the nightly before filing this! > > I just tried to verify in the latest nightly build (r191040), but the bug > still reproduced. But I'm actually not sure the nightly WebKit was being > used (maybe due to System Integrity Protection?); navigator.userAgent didn't > mention the nightly build at all. > > Is there something special I need to do to use nightly builds on El Capitan? Not that I know of. (cc: ddkilzer) I downloaded the nightly and the attached test case works fine with it. (see attachment)
alan
Comment 6 2015-10-14 08:17:45 PDT
Created attachment 263077 [details] Verified on nightly
Adam Roben (:aroben)
Comment 7 2015-10-15 12:19:23 PDT
> Is there something special I need to do to use nightly builds on El Capitan? I filed bug 150180 about this.
Note You need to log in before you can comment on or make changes to this bug.