1750985 - translate3d moves Youtube video's clickable area

Status: RESOLVED DUPLICATE of bug 1753779

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

Description

[Gabor]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0

Steps to reproduce:

Visit this example:
https://jsfiddle.net/mowar/8hk1wx05/2/

Actual results:

You cannot click on the video.

Another test case result:
If you change the CSS values of the #container to rather use 100px:
#container{
transform: translate3d(0px, -100px, 0px);
padding-top:100px;
}

you can see, that you only cannot click the bottom 100px area of the video, because all clickable/hoverable areas are moved 100px higher from their actual placement. If you start the video where you can click on it, you can also see this on the controls and timeline, that everything is 100px off.

Expected results:

You should be able to click on the video in its area, and once the video is started, its controls and timeline should also still be useable.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Alice0775 White]

I canreproduce the issue in Nightly98.0a1 Windows10.
Disabling Fission solves this issue.

Comment 3

[Edgar Chen [:edgar] (PTO until 02/09)]

The symptoms are very similar to bug 1745834.

Comment 4

[Timothy Nikkel (:tnikkel)]

Maybe this is solved by your recent work?

Comment 5

[Botond Ballo [:botond]]

I can't reproduce this, even in Nightly builds before bug 1745834 with Fission enabled.

However, due to the similarity of the symptoms, it's worth re-testing especially after the follow-up bug 1765204 lands.

Comment 6

[Botond Ballo [:botond]]

Gabor, would you be able to check the latest Firefox Nightly (which contains the fix for bug 1765204) and see if the issue is still reproducible there for you?

Comment 7

[Gabor]

Hi Botond!

Firefox Nightly seems to work fine!

Comment 8

[Edgar Chen [:edgar] (PTO until 02/09)]

I could not reproduce in Nightly.
I ran mozregression with --find-fix and got

20:14.63 INFO: First good revision: 40024584d0215990127ecb4e5900a593eec78086
20:14.63 INFO: Last bad revision: b79377e42171c1ae94e4e439e28c76d39d8a9755
20:14.63 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b79377e42171c1ae94e4e439e28c76d39d8a9755&tochange=40024584d0215990127ecb4e5900a593eec78086