Bug 34181

Summary: RTL content displays ghost text shifted far from the content
Product: WebKit Reporter: Tim McConnell <timmc>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: leviw, mitz, playmobil, tonikitoo, xji, yael
Priority: P3    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
Attachments:
Description Flags
The root HTML file needed for the repro.
none
The HTML file for the IFrame content.
none
The style sheet used in the IFrame content.
none
Decorative image #1.
none
Decorative image #2. none

Tim McConnell
Reported 2010-01-26 13:07:00 PST
Certain markup + CSS cause Safari to render strange artifacts in RTL. This bug requires the repro files to understand.
Attachments
The root HTML file needed for the repro. (534 bytes, text/html)
2010-01-26 13:09 PST, Tim McConnell
no flags
The HTML file for the IFrame content. (74.75 KB, text/html)
2010-01-26 13:14 PST, Tim McConnell
no flags
The style sheet used in the IFrame content. (4.86 KB, text/css)
2010-01-26 13:18 PST, Tim McConnell
no flags
Decorative image #1. (75 bytes, image/gif)
2010-01-26 13:40 PST, Tim McConnell
no flags
Decorative image #2. (75 bytes, image/gif)
2010-01-26 16:14 PST, Tim McConnell
no flags
Tim McConnell
Comment 1 2010-01-26 13:09:59 PST
Created attachment 47439 [details] The root HTML file needed for the repro. This file requires another HTML file and its CSS file.
Tim McConnell
Comment 2 2010-01-26 13:14:02 PST
Created attachment 47442 [details] The HTML file for the IFrame content.
Tim McConnell
Comment 3 2010-01-26 13:18:35 PST
Created attachment 47443 [details] The style sheet used in the IFrame content.
Tim McConnell
Comment 4 2010-01-26 13:40:51 PST
Created attachment 47444 [details] Decorative image #1.
Tim McConnell
Comment 5 2010-01-26 16:14:27 PST
Created attachment 47457 [details] Decorative image #2.
Levi Weintraub
Comment 6 2011-01-13 13:52:27 PST
This repro in Safari 5.0.3, but not in TOT WebKit, nor the latest Dev channel build of Chrome. Looks like this has been resolved (though I'm not sure how/where).
Note You need to log in before you can comment on or make changes to this bug.