RESOLVED FIXED 119011
Web Inspector: using cmd+tab to leave the inspector window forces "jump to definition" mode when it gains focus again 
https://bugs.webkit.org/show_bug.cgi?id=119011
Summary Web Inspector: using cmd+tab to leave the inspector window forces "jump to de...
Antoine Quint
Reported 2013-07-23 07:14:19 PDT
Steps to reproduce: 1. Open the inspector (docked or not, doesn't matter) 2. Open the styles panel 3. Cmd+tab to switch to another application 4. Cmd+tab to switch back to Safari At this point, if you mouse over a CSS property name, it'll underline and a click will jump to where the property was defined. We're probably detecting the Cmd key being pressed from the Cmd+tab action as we lose focus since this only happens if you Cmd+tab away from the window.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2013-07-23 07:14:35 PDT
<rdar://problem/14521065>
Timothy Hatcher
Comment 2 2013-07-23 07:53:33 PDT
Great! We have had a user on Twitter reporting this be we could never find steps.
Antoine Quint
Comment 3 2013-10-02 07:19:54 PDT
This is due to WebInspector.modifierKeys.metaKey having the incorrect value in this scenario. I'm not sure how we can get updated information about the metaKey press state as the window regains focus.
Antoine Quint
Comment 4 2013-10-02 10:51:18 PDT
One way to do this would be to track key modifier states on mousemove events at the window level, as well as on keypress. I think that would give us the most comprehensive coverage. Additionally, I think we would do well to also track the mouse coordinates at all times in case they need to be queried. This could be useful for some of the CodeMirror-related features that we're implementing (such as http://webkit.org/b/119012) where we may need to get information about a token outside of a mouse event, for instance when the key modifier states change.
Antoine Quint
Comment 5 2013-10-03 08:27:45 PDT
The patch for review in http://webkit.org/b/119012 fixes this.
Antoine Quint
Comment 6 2013-10-05 01:16:34 PDT
Fixed with http://trac.webkit.org/changeset/156923.
Note You need to log in before you can comment on or make changes to this bug.