1318635 - timeStamp of "dblclick" is always 0 in release build

Status: RESOLVED FIXED

(Core :: DOM: UI Events & Focus Handling, defect)

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Attachment: Bug 1318635 Set "dblclick" event's time and timeStamp to mouseup event's time and timeStamp

Review commit: https://reviewboard.mozilla.org/r/94010/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/94010/

Comment 2

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Smaug, would you like to review it? (I wonder, who can review around event handling during your vacation.)

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

I think we really should just focus on fixing bug 1026804. As far as I know, Chrome is already shipping highres timestamps. (but better to test and verify).

But yes, looks like the patch ensures both old and high res timestamp.

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Comment on attachment 8812142 [details]
Bug 1318635 Set "dblclick" event's time and timeStamp to mouseup event's time and timeStamp

https://reviewboard.mozilla.org/r/94010/#review94156

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/dcf886cf73de
Set "dblclick" event's time and timeStamp to mouseup event's time and timeStamp r=smaug

Comment 6

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/dcf886cf73de