Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

suppressEvents accepts focus but not reload event

0 views
Skip to first unread message

John J. Barton

unread,
Dec 20, 2009, 1:17:16 AM12/20/09
to
Recently we started calling suppressEvents when Firebug stops on a
breakpoint. However this causes an anomaly: the DOMWindow accepts focus
but not events. For example, control-R fails to reload but only if you
happen to have focus on the now frozen window. Should this be a bug?

jjb

Boris Zbarsky

unread,
Dec 20, 2009, 4:20:55 PM12/20/09
to

I'm not sure what the problem is, based on the above. It's probably
worth filing a bug with clear expected and actual results, steps to
reproduce, etc...

-Boris

Smaug

unread,
Dec 21, 2009, 6:37:10 PM12/21/09
to
On 12/20/09 8:17 AM, John J. Barton wrote:
> Recently we started calling suppressEvents when Firebug stops on a
> breakpoint. However this causes an anomaly: the DOMWindow accepts focus
> but not events.
I'm not sure what this means. If the window has focus, calling
suppressEvents doesn't move the focus anywhere. If some other DOM
Window is focused and user clicks a DOM Window in which events are
suppressed, no focus event should be dispatched.

> For example, control-R fails to reload but only if you
> happen to have focus on the now frozen window.

This sounds like to correct behavior (at least per how we handle
shortcut keys); the key event goes to the focused element, but if
events (key/mouse/etc) are suppressed, the event isn't dispatched to
anywhere.


> Should this be a bug?

Feel free to file, CC me.
And please explain what kind of behavior Firebug would need.

-Olli


>
> jjb

John J Barton

unread,
Dec 21, 2009, 9:17:40 PM12/21/09
to
Smaug wrote:
> On 12/20/09 8:17 AM, John J. Barton wrote:
>> Recently we started calling suppressEvents when Firebug stops on a
>> breakpoint. However this causes an anomaly: the DOMWindow accepts focus
>> but not events.
> I'm not sure what this means. If the window has focus, calling
> suppressEvents doesn't move the focus anywhere. If some other DOM
> Window is focused and user clicks a DOM Window in which events are
> suppressed, no focus event should be dispatched.

Hmm, may be this is the hint: perhaps we should force focus into Firebug
when we hit the breakpoint. If the user clicks on a frozen window, will
Firefox give it focus (even if no events fire)? It seems not, at least
if I manually give Firebug focus while on a breakpoint, then clicking on
the (frozen) window does not cause the anomalous behavior with control-r.

Thanks!
jjb

0 new messages