1463363 - Vimeo content disappears after opening a video in a new tab by middle clicking it

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect, P1)

Description

[Cristian Baica [:cbaica], Release Desktop QA]

Attachment: vimeo content disappears

[Affected versions]: 
- Fx 60.0.1 buildID: 20180516032328
- Fx 61.0b7 buildID: 20180521110957
- Fx 62.0a1 buildID: 20180521220045

[Affected platforms]:
- Windows 10 x64
- macOS 10.3.4
- Ubuntu 16.04 x64

[Steps to reproduce]:
1. Launch Firefox.
2. Go to www.vimeo.com/watch
3. Middle click on one of the available videos.

[Expected result]:
- A new tab is opened without any changes to the current page.

[Actual result]:
- A new tab is opened but all the content disappears from the current page.

[Regression range]:
I don't think this is a regression since I could reproduce the issue on Fx 34.0a1. This might be related to the changes Vimeo did to their website.

[Additional notes]:
If a video is opened as described in the steps from the vimeo.com page, the issue does not occur.

Comment 1

[Mike Taylor [:miketaylr]]

This doesn't reproduce for me on Mac, but it does for Sergiu on Win10 -- we should figure out what's up.

Sergiu, can you add any relevant info for debugging? Thanks.

Comment 2

[Mike Taylor [:miketaylr]]

Actually, I can reproduce (watching the video helps :)).

Karl, can you take a look? This seems like a CSS / JS interaction.

Comment 3

[Karl Dubost💡 :karlcow]

I can't reproduce on macOS 10.13.4 (17E202)
with Firefox Nightly 62.0a1 (2018-05-30) (64-bit)
and trackpack Command + Tap

Mike, Does it happen for you with the trackpad too?

Comment 4

[Mike Taylor [:miketaylr]]

No, only with my external mouse.

Comment 5

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 6

[Karl Dubost💡 :karlcow]

This is the log of command click in the debugger

• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } gtm js:17510:49
• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } fbevents.js:25
• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } react_prod_combined.min.js:5:27211
• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } explore_combined.min.js:2:31848
• topClick react_prod_combined.min.js:4:10872
• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } gtm.js:17588:79
• click { target: div.iris-annotation-layer.iris_annotation.iris_annotation--videovitals.iris_annotation--sm, buttons: 0, clientX: 1008, clientY: 606, layerX: 170, layerY: 55 } gtm.js:17568:127

​
mike, do you have the same sequence with the mouse

https://f.vimeocdn.com/js_opt/react_prod_combined.min.js?f57646b3

    case 'topClick':
      if (2 === n.button) return null;

https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/button
for me obviously n.button is 0
for you it should be n.button === 1 (?)

Comment 7

[Mike Taylor [:miketaylr]]

This no longer reproduces with an external mouse. I get expected results now.