Closed
Bug 1463363
Opened 6 years ago
Closed 4 years ago
Vimeo content disappears after opening a video in a new tab by middle clicking it
Categories
(Web Compatibility :: Site Reports, defect, P1)
Tracking
(firefox-esr60 wontfix, firefox60 wontfix, firefox61 wontfix, firefox62 wontfix)
People
(Reporter: cbaica, Unassigned)
References
()
Details
(Keywords: webcompat:needs-diagnosis, Whiteboard: [needsdiagnosis])
Attachments
(1 file)
7.85 MB,
video/mp4
|
Details |
[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•6 years ago
|
||
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.
Flags: needinfo?(sergiu.logigan)
Priority: -- → P1
Whiteboard: [needsdiagnosis]
Comment 2•6 years ago
|
||
Actually, I can reproduce (watching the video helps :)). Karl, can you take a look? This seems like a CSS / JS interaction.
Flags: needinfo?(sergiu.logigan) → needinfo?(kdubost)
Comment 3•6 years ago
|
||
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?
Flags: needinfo?(kdubost)
Comment 4•6 years ago
|
||
No, only with my external mouse.
Assignee | ||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
Comment 5•5 years ago
|
||
See bug 1547409. Moving webcompat whiteboard tags to keywords.
Keywords: webcompat:needs-diagnosis
Comment 6•4 years ago
|
||
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 (?)
Flags: needinfo?(miket)
Comment 7•4 years ago
|
||
This no longer reproduces with an external mouse. I get expected results now.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(miket)
Resolution: --- → WORKSFORME
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•