Summary: | REGRESSION: Node highlight not updated properly | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Matt Lilek <dev+webkit> | ||||
Component: | Web Inspector (Deprecated) | Assignee: | Adam Roben (:aroben) <aroben> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | aroben | ||||
Priority: | P1 | Keywords: | InRadar, PlatformOnly, Regression | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
URL: | data:text/html,<div style="width: 500px; height: 50px; background: red;">Top</div><div style="position: absolute; top: 1500px; width: 500px; height: 50px; background: green;">Bottom</div> | ||||||
Attachments: |
|
Description
Matt Lilek
2008-02-01 09:40:58 PST
(In reply to comment #0) > After Adam's reworking of the node highlight code yesterday [snip] For future reference, that would be the following check ins: <http://trac.webkit.org/projects/webkit/changeset/29886> <http://trac.webkit.org/projects/webkit/changeset/29887> <http://trac.webkit.org/projects/webkit/changeset/29888> I think the problem is that we translate the context before scrolling the element into view, which could change how much we need to translate by. Created attachment 18988 [details]
patch with changelog
Comment on attachment 18988 [details]
patch with changelog
r=me
+ context.translate(-overlayRect.x(), -overlayRect.y());
Should we use save/restore instead?
(In reply to comment #5) > (From update of attachment 18988 [details] [edit]) > + context.translate(-overlayRect.x(), -overlayRect.y()); > > Should we use save/restore instead? I think it would be "in addition to" rather than "instead". I think we could save/restore in case the InspectorClient wanted to do more drawing of its own, but since the hope is that all drawing will go through this method I don't think it's really necessary. |