Open Bug 1470377 Opened 2 years ago Updated 15 hours ago
Video context menu does not stay on screen and it pauses the video on Twitter
[Affected versions]: - Firefox 61.0build3 - Latest Nightly 62.0a1 - Firefox 52.9.0esr [Affected platforms]: - macOS 10.13 - Ubuntu 18.04 64bit [Unaffected platforms]: - Windows 10 64bit - Windows 7 64bit [Steps to reproduce]: 1. Start Firefox 2. Visit any twitter page that has a video (eg: https://twitter.com/IEM) 3. Scroll down the page to a video 4. Start the video (if it does not start on focus) and right click on it [Expected result]: - Context menu opens and user can copy video address. [Actual result]: - Context menu does not stay on page, the user is unable to click Copy video address unless right click is kept pressed and hover over the button, then left click. [Regression range]: - This is not a recent regression since it reproduces back to 52.7esr and 57RC. Will investigate further to see if it's an old regression ASAP. [Additional notes]: - On Windows operating systems the video is paused on right click but the context menu does not disappear, which again I'm not sure if it's the right behaviour here. - Chrome does not manifest either of these behaviours.
Here is a screencast showing the issue
Pretty sure that context menu is provided by twitter and not by us, so if anything I suspect this is a site issue on twitter.com .
Component: Video/Audio Controls → Desktop
Product: Toolkit → Tech Evangelism
Hrm, I can't get a context menu in Firefox or Chrome, right-click just pauses for me.
On older builds e.g. Firefox 10, Firefox 20, Firefox 30 the video container is not displayed and from Firefox 40 to 45 it shows the following message error "We cannot play the video in this browser. Please try a different web browser". On Firefox 45 the video container is shown but you can't play the video instead if right click on video container the context menu is shown and it doesn't stay. Based on the above it doesn't seem to be a regression.
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.