Bug 146872

Summary: [iOS WK2] Scrolling issues on horizontally scrollable RTL pages
Product: WebKit Reporter: Simon Fraser (smfr) <simon.fraser>
Component: New BugsAssignee: Simon Fraser (smfr) <simon.fraser>
Status: RESOLVED FIXED    
Severity: Normal CC: sabouhallawa, simon.fraser, thorton
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch
none
Patch sam: review+

Simon Fraser (smfr)
Reported 2015-07-10 22:14:26 PDT
[iOS WK2] Scrolling issues on horizontally scrollable RTL pages
Attachments
Patch (22.65 KB, patch)
2015-07-10 22:24 PDT, Simon Fraser (smfr)
no flags
Patch (26.97 KB, patch)
2015-07-10 23:41 PDT, Simon Fraser (smfr)
no flags
Patch (27.02 KB, patch)
2015-07-11 10:51 PDT, Simon Fraser (smfr)
sam: review+
Simon Fraser (smfr)
Comment 1 2015-07-10 22:24:57 PDT
Simon Fraser (smfr)
Comment 2 2015-07-10 23:41:45 PDT
Simon Fraser (smfr)
Comment 3 2015-07-11 10:51:12 PDT
Sam Weinig
Comment 4 2015-07-11 10:58:11 PDT
Comment on attachment 256657 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=256657&action=review > Source/WebKit2/Shared/mac/RemoteLayerTreeTransaction.mm:1250 > + dumpProperty(ts, "transactionID", m_transactionID); If we ever use this for tests, will putting the transactionID in the dump make it inconsistent. Or will we use a different dumping mechanism for testing.
Simon Fraser (smfr)
Comment 5 2015-07-11 11:21:43 PDT
Tim Horton
Comment 6 2015-07-11 15:11:39 PDT
(In reply to comment #4) > Comment on attachment 256657 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=256657&action=review > > > Source/WebKit2/Shared/mac/RemoteLayerTreeTransaction.mm:1250 > > + dumpProperty(ts, "transactionID", m_transactionID); > > If we ever use this for tests, will putting the transactionID in the dump > make it inconsistent. Or will we use a different dumping mechanism for > testing. I can't imagine that being any worse than the layer IDs, which are already in there.
Note You need to log in before you can comment on or make changes to this bug.