Odd. The case with inlined styles does not work to reproduce the issue (i.e. its behaviour is correct). Please download attachment #8458063 [details] instead.
Attachment #8458071 - Attachment is obsolete: true
Attachment #8458063 - Attachment is obsolete: false
I've created a minimal test case that reproduces the problem. Still looking into why it happens.
Forgot to repeat the STR: 1. Open attachment 8458698 [details] in a tab and open the debugger. 2. Go to the events pane and click to break on mouseout events. 3. Move the mouse cursor over the button and hit F8 to pause. 4. Observe that leaving the content window will run the event handler and not pause execution (although I've got a pause at one time).
Assignee: nobody → past
Status: NEW → ASSIGNED
Priority: -- → P3
I suspect that this is related to bugs 801304 and 1044074. The gist of those bugs is that nested event loops don't properly suppress all events. Something similar might be going on here.
No time for this in the near future unfortunately.
Assignee: past → nobody
Status: ASSIGNED → NEW
Whiteboard: [devtools-platform] → [debugger-mvp] [devtools-platform]
Status: NEW → RESOLVED
Last Resolved: 23 hours ago
Resolution: --- → FIXED
Whiteboard: [debugger-mvp] [devtools-platform] → [devtools-platform]
You need to log in before you can comment on or make changes to this bug.