Bug 157471

Summary:

-webkit-isolate incorrectly measures width of inline elements

Product:

WebKit

Reporter:

Derk-Jan Hartman <hartman.wiki>

Component:

CSS

Assignee:

Myles C. Maxfield <mmaxfield>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

bfulgham, mmaxfield, simon.fraser, zalan

Priority:

Version:

Safari 9

Hardware:

Unspecified

OS:

Unspecified

Attachments:

Description	Flags
Page with css statement applied	none
Page with css statement disabled	none
webarchive of page in the screenshots	none
Test reduction	none

Derk-Jan Hartman

Reported 2016-05-09 04:04:46 PDT

Created attachment 278399 [details] Page with css statement applied Although the tab lockup of #148573 seems fixed in Safari 9, it seems that it is incorrectly measuring the width of inline elements (spanning multiple lines ???). Content overflows outside of the expected boundaries and random spacing is introduced between words. Attached are a screenshot of a page with -webkit-isolate enabled on the .comment class, a screenshot with the rule disabled and a webarchive of the page. This problem does not occur in Chrome.

Attachments
Page with css statement applied (1.17 MB, image/png) 2016-05-09 04:04 PDT, Derk-Jan Hartman	no flags	Details
Page with css statement disabled (1.49 MB, image/png) 2016-05-09 04:05 PDT, Derk-Jan Hartman	no flags	Details
webarchive of page in the screenshots (490.69 KB, application/x-webarchive) 2016-05-09 04:05 PDT, Derk-Jan Hartman	no flags	Details
Test reduction (852 bytes, text/html) 2016-05-10 11:58 PDT, alan	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Derk-Jan Hartman

Comment 1 2016-05-09 04:05:11 PDT

Created attachment 278400 [details] Page with css statement disabled

Derk-Jan Hartman

Comment 2 2016-05-09 04:05:48 PDT

Created attachment 278401 [details] webarchive of page in the screenshots

alan

Comment 3 2016-05-10 11:58:24 PDT

Created attachment 278517 [details] Test reduction

Brent Fulgham

Comment 4 2022-07-14 15:42:00 PDT

Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.

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