RESOLVED DUPLICATE of bug 14276 14458
Web Inspector Opens Behind Current Window
https://bugs.webkit.org/show_bug.cgi?id=14458
Summary Web Inspector Opens Behind Current Window
Ryan
Reported 2007-06-29 08:57:20 PDT
Not sure if this is the intended behavior, but it sure is annoying. Every time I select "inspect element" the inspector appears in a jerky drawing process that goes like this: 1) webkit draws the outline of the inspector on top of the current window 2) webkit applies a black mask over the current window and the portion of the outline of the inspector window that falls over the current window 3) inspector window is moved behind current window I have a fast computer and there's really no reason it should not be a smooth process to open a new window.
Attachments
mitz
Comment 1 2007-06-29 11:34:44 PDT
Thanks for the bug report, Ryan. While my computer isn't the fastest, I don't see the inspector moving behind the current window at any stage. Do you have any Safari "enhancers", input managers, Haxies or extensions installed?
Adam Roben (:aroben)
Comment 2 2007-06-29 11:39:33 PDT
(In reply to comment #1) > Thanks for the bug report, Ryan. While my computer isn't the fastest, I don't > see the inspector moving behind the current window at any stage. Do you have > any Safari "enhancers", input managers, Haxies or extensions installed? Ryan is reporting this issue on Windows, which has entirely separate code for showing the inspector and overlay.
mitz
Comment 3 2007-06-29 12:00:21 PDT
(In reply to comment #2) > Ryan is reporting this issue on Windows, which has entirely separate code for > showing the inspector and overlay. > Oops. I guess I should start paying attention to the OS field.
Ryan
Comment 4 2007-06-29 12:00:41 PDT
mitz: No extensions or add-ons installed. Adam: Thanks for pointing that out.
Robert Blaut
Comment 5 2007-08-30 03:18:19 PDT
Confirmed in Webkit Nigthly r25282.
Adam Roben (:aroben)
Comment 6 2008-03-13 23:12:10 PDT
Seems related to bug 14276.
Robert Blaut
Comment 7 2008-06-10 23:43:22 PDT
(In reply to comment #6) > Seems related to bug 14276. > It's a dubicate of bug 14276 which is already fixed. I've tested the issue in Webkit r34388 and I can confirm the bug is no longer visible. *** This bug has been marked as a duplicate of 14276 ***
Note You need to log in before you can comment on or make changes to this bug.