Bug 1636555 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I can reproduce in Nightly 2018-12-01 as well (i.e. version 65.0a1 (2018-12-01) (64-bit))

I tried a somewhat older Nightly, 2018-06-01, but you can't complete the STR there because clicking the thumbnail image triggers a JS error `ReferenceError: event is not defined` when I click the thumbnail -- so they must be using some JS/DOM feature that we added more recently than that.

So: bottom line, this doesn't seem to be a regression (not in Firefox at least).  This may be a Xorg/Ubuntu regression or behavior-change involved, or possibly not; I don't have older Ubuntu handy for testing.
Revision 1 by
on 
I can reproduce in Nightly 2018-12-01 as well (i.e. version 65.0a1 (2018-12-01) (64-bit))

I tried a somewhat older Nightly, 2018-06-01, but you can't complete the STR there because clicking the thumbnail image triggers a JS error `ReferenceError: event is not defined` when I click the thumbnail, and nothing happens (the image slideshow in-content-modal-popup doesn't appear) -- so they must be using some JS/DOM feature that we added more recently than that.

So: bottom line, this doesn't seem to be a regression (not in Firefox at least).  This may be a Xorg/Ubuntu regression or behavior-change involved, or possibly not; I don't have older Ubuntu handy for testing.
Revision 2 by
on 
I can reproduce in Nightly 2018-12-01 as well (i.e. version 65.0a1 (2018-12-01) (64-bit))

I tried a somewhat older Nightly, 2018-06-01, but you can't complete the STR there because clicking the thumbnail image triggers a JS error `ReferenceError: event is not defined` when I click the thumbnail, and nothing happens (the image slideshow in-content-modal-popup doesn't appear) -- so they must be using some JS/DOM feature that we added between those two Nightlies. (Not that that feature is involved with the graphics error; it's just required to get to the spot that triggers the graphics error.)

So: bottom line, this doesn't seem to be a regression (not in Firefox at least).  This may be a Xorg/Ubuntu regression or behavior-change involved, or possibly not; I don't have older Ubuntu handy for testing.

Back to Bug 1636555 Comment 4