Bug 127823

Summary: [iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries
Product: WebKit Reporter: Andy Estes <aestes>
Component: New BugsAssignee: Andy Estes <aestes>
Status: RESOLVED FIXED    
Severity: Normal CC: dbates, ddkilzer, simon.fraser, thorton
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
[iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries dbates: review+

Andy Estes
Reported 2014-01-28 18:36:54 PST
[iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries
Attachments
[iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries (2.80 KB, patch)
2014-01-28 18:39 PST, Andy Estes
dbates: review+
Andy Estes
Comment 1 2014-01-28 18:37:08 PST
Andy Estes
Comment 2 2014-01-28 18:39:21 PST
Created attachment 222541 [details] [iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries
Daniel Bates
Comment 3 2014-01-28 18:41:06 PST
Comment on attachment 222541 [details] [iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries OK. Feel free to get a rendering expert to provide a more thorough review.
Daniel Bates
Comment 4 2014-01-28 18:55:55 PST
Comment on attachment 222541 [details] [iOS] REGRESSION (r162663): Webpages have strange artifacts or corruption around tile boundaries View in context: https://bugs.webkit.org/attachment.cgi?id=222541&action=review > Source/WebCore/platform/ScrollView.cpp:385 > + IntSize scrollSize = m_contentsSize - visibleContentRect(LegacyIOSDocumentViewRect).size(); Notice that LegacyIOSDocumentViewRect is only defined when building for iOS. Instead we should use LegacyIOSDocumentVisibleRect, which is defined to be LegacyIOSDocumentViewRect and ContentsVisibleRect on iOS and non-iOS ports, respectively.
Andy Estes
Comment 5 2014-01-28 19:01:32 PST
Note You need to log in before you can comment on or make changes to this bug.