Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 160510 No way to inspect an element without triggering a blur event
Starred by 8 users Reported by m...@elv1s.ru, Nov 12 2012 Back to list
Status: Fixed
Owner:
User never visited
Closed: Apr 2014
Cc:
Components:
NextAction: ----
OS: All
Pri: 2
Type: Bug


Sign in to add a comment
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.5 Safari/537.17

Steps to reproduce the problem:
Screencast of the problem: http://www.screenr.com/umH7

1. Open http://jqueryui.com/autocomplete/
2. Type "a" in the input field
3. Press Ctrl + Shift + i (Cmd + Shift + i on Mac OS X) to inspect the autocomplete widget

What is the expected behavior?
The widget does’t hide so I can inspect it freely.

What went wrong?
The widget hides because the current page becomes inactive and a blur event occurs on the input field.

Did this work before? No 

Chrome version: 24.0.1312.5  Channel: dev
OS Version: OS X 10.8.2

http://stackoverflow.com/questions/13296992/how-do-i-debug-and-inspect-things-that-change-on-response-to-mouseclicks-or-focu
 
Comment 1 by dharani@google.com, Nov 12 2012
Labels: Action-BisectNeeded
Labels: -Action-BisectNeeded
Owner: apavlov@chromium.org
Status: Assigned
Labels: -Via-Wizard Action-FeedbackNeeded
Please try the following:

1. Open the docked DevTools first (the undocked approach will not work due to the OS limitations.)
2. Once the autocomplete box is displayed, right-click it and select "Inspect Element" in the context menu. The focus will move to the DevTools but the autocomplete box will still be shown (this worked for me on Linux, Chrome Canary 25. Your mileage may vary.)

Does this work for you?
Comment 5 by m...@elv1s.ru, Nov 21 2012
It doesn’t. You can see it on http://www.screenr.com/umH7 at 0:13.
Labels: -Action-FeedbackNeeded
Thanks. I'm afraid this is also an OS limitation. I'll see if there's something that can be done about it.
Project Member Comment 7 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Feature-DevTools Cr-Platform-DevTools
Comment 8 by v...@vdm.ie, Mar 27 2014
This issue reproduced in Firefox 30.0a2 (2014-03-25) for Mac. However, it is possible to pause the debugger in Firefox and inspect the autocomplete div, but not in Chrome. In Chrome hitting pause unblurs the <input> and loses the <div>.
Project Member Comment 9 by bugdroid1@chromium.org, Apr 8 2014
------------------------------------------------------------------
r262492 | apavlov@chromium.org | 2014-04-08T20:04:02.278394Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/devtools/devtools_window.h?r1=262492&r2=262491&pathrev=262492
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/devtools/devtools_embedder_message_dispatcher.cc?r1=262492&r2=262491&pathrev=262492
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/browser.cc?r1=262492&r2=262491&pathrev=262492
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/devtools/devtools_embedder_message_dispatcher.h?r1=262492&r2=262491&pathrev=262492
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/devtools/devtools_window.cc?r1=262492&r2=262491&pathrev=262492

DevTools: Forward whitelisted unhandled shortcuts from inspected page into DevTools frontend

This will allow to freeze the inspected page,
so that the focus loss will not alter its state.

This is the Chromium part of the change.

R=pfeldman
BUG= 160510 

Review URL: https://codereview.chromium.org/225973003
-----------------------------------------------------------------
Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Tested the same on mac 10.9 chrome version 36.0.1933.0 (Official Build 262849) canary as per comment #4 - observed that after the focus changed to the dev tools the autocomplete drop down box on the page disappears. 

Could you please let us know if i am missing something here. If this is the issue it is still present post the revision  r262492 . Please confirm
Project Member Comment 11 by bugdroid1@chromium.org, Apr 14 2014
The following revision refers to this bug:
  http://src.chromium.org/viewvc/blink?view=rev&rev=171463

------------------------------------------------------------------
r171463 | apavlov@chromium.org | 2014-04-14T14:22:21.416563Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/trunk/LayoutTests/inspector/sources/debugger/debugger-step-into-custom-element-callbacks.html?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/externs.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/LayoutTests/http/tests/inspector/debugger-test.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/devtools.gypi?r1=171463&r2=171462&pathrev=171463
   A http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/ForwardedInputEventHandler.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/scripts/frontend_modules.json?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/web/InspectorFrontendClientImpl.cpp?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/inspector.html?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/InspectorFrontendAPI.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/InspectorFrontendHostStub.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/SourcesPanel.js?r1=171463&r2=171462&pathrev=171463
   M http://src.chromium.org/viewvc/blink/trunk/Source/devtools/front_end/Main.js?r1=171463&r2=171462&pathrev=171463

DevTools: Handle the F8 shortcut forwarded from the inspected page

R=pfeldman, vsevik
BUG= 160510 

Review URL: https://codereview.chromium.org/225873004
-----------------------------------------------------------------
Labels: -OS-Mac -Needs-Feedback OS-All
Status: Fixed
Now pressing F8 in the inspected page (when DevTools are opened) will halt JS execution, and no focus loss will occur.
Comment 13 by ke...@brogan.ca, Aug 18 2014
This has regressed. Sure you can f12 and then f8, but if you f12, click on the page so that it has focus again, then f8... nothing.
@kevin: what Chrome version are you using?
Sign in to add a comment