Closed GoogleCodeExporter closed 8 years ago
Some more observations on this issue.
In Internet Explorer, I can't reproduce the problem. No matter how quickly I
repeatedly
activate the trigger, the counter only ever increments in single units.
In Chrome, the situation is worse. Every time the trigger is activated the
counter
increments by at least two, even when there is a lengthy pause between
activations.
Sometimes the counter is incremented by three for a single activation.
Original comment by phil.boo...@gtempaccount.com
on 21 Sep 2009 at 11:32
Updating the labels.
Original comment by phil.boo...@gtempaccount.com
on 23 Sep 2009 at 10:52
Original comment by phil.boo...@gtempaccount.com
on 28 Sep 2009 at 3:09
Original comment by phil.boo...@gtempaccount.com
on 28 Sep 2009 at 3:11
There are actually two problems at work here.
Firstly, the click and dblclick events do not appear to be mutually exclusive
in
Firefox and Safari, as they are in Internet Explorer. Thus, by mapping both
events to
DOMActivate as we currently do, we cause three DOMActivate events to be
dispatched
when a user double clicks on a trigger.
Secondly, Safari actually dispatches the DOMActivate correctly itself, unlike
the
other two browsers. Therefore, when we call mapclick2domactivate() in Safari,
we are
ensuring that every click results in two DOMActivate events being dispatched.
Original comment by phil.boo...@gtempaccount.com
on 30 Sep 2009 at 12:10
A proposed fix is awaiting review at r3022.
Original comment by phil.boo...@gtempaccount.com
on 30 Sep 2009 at 12:33
The fix proposed at r3022 actually causes a weird refresh problem, described in
issue
574. So I'm reverting the status of this issue to Started and working on a new
proposal
for this issue now.
Original comment by phil.boo...@gtempaccount.com
on 1 Oct 2009 at 2:23
A revised proposed fix is awaiting review at r3028.
Original comment by phil.boo...@gtempaccount.com
on 1 Oct 2009 at 3:00
In trunk at r3030.
Original comment by phil.boo...@gtempaccount.com
on 2 Oct 2009 at 1:58
Original issue reported on code.google.com by
phil.boo...@gtempaccount.com
on 21 Sep 2009 at 11:20Attachments: