Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 65.0.3325.146 using Mac 10.13.1 with the below mentioned steps.
1. Launched chrome
2. Downloaded "fullscreen-test.html" and opened in a new tab
3. Inspected the page -> console
4. Clicked on the button
We observed "hi" message has been logged in console every time we click the button. In between we maximised  the window and tried setting full screen mode by zooming in the page. Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if we have missed anything in the process. Any further inputs from your end may help us to triage the issue in a better way.

Deleted: 821576.mp4 6.1 MB

	821576.mp4 6.1 MB View Download

Hi!

Thanks for your prompt feedback. The screencast doesn't follow the listed steps to reproduce the problem. The problem occurs when a video element is entered in fullscreen, not when you're zoomed in. Zooming in on the video element and toggling it into fullscreen are not equivalent. You will have to ensure the video element actually loads, and enter into fullscreen by pressing the fullscreen toggle on the controls, as stated in the steps to reproduce. 

You will have to either upload that file to a third party hosting service or access it via running your local server - the video needs to load in order for it to be an accurate test. Visiting the link included in the ticket will also load the page properly.

I've attached a screencast of myself reproducing the problem. Please let me know if you have any further questions, and thanks again for your help.  

Deleted: Chromium-Fullscreen-Issue.zip 25.2 MB

Chromium-Fullscreen-Issue.zip 25.2 MB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The attachment/video provided in comment#3 was very helpful in understanding the issue being faced.

@christina: From our end, after opening the test file in a new tab, we are unable to play the video, so that we can check it by clicking full screen mode. It would be highly helpful if provided with another test file which allows us to play the video. As we are not very clear about the process of uploading a file to a third party hosting service or accessing it via running local server.

Thanks! 

I've attached another version of the test file - you should be able to open it in a normal browser tab now, without additional steps. Please let me know if that is not the case. 

Deleted: fullscreen-test.html 488 bytes

fullscreen-test.html 488 bytes View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Not quite sure why fullscreen is required to repro this (but it appears to be). None the less it looks like an input issue, over to the input team for clarification.

Able to reproduce the issue on reported chrome version 65.0.3325.146 and on the latest canary 67.0.3371.0 with the test file provided in comment#6 using Windows 10, Ubuntu 14.04 and Mac 10.13.1.

Bisect Information:
====================
Last Good Build: 65.0.3288.0
First Bad Build: 65.0.3289.0

You are probably looking for a change made after 522770 (known good), but no later than 522771 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/3b0721d2e0a2f632436646b89648959f69a9dce9..17dd72fb55aaa071bf1077a02e45b9f2f44d1ed2

Suspecting: https://chromium.googlesource.com/chromium/src/+/17dd72fb55aaa071bf1077a02e45b9f2f44d1ed2

Review URL: https://chromium-review.googlesource.com/788052

@Philip Jägenstedt: Please help in assigning it to the right owner if this is not related to your change.

Note: Adding RB-Stable as this is a recent regression, Please feel free to remove if not needed.

Thanks!

Moving this to RB-Beta because:
- foolip@ is only back on Tuesday and there is no obvious owner to tackle this in a better time frame;
- there is no obvious real world effect we've heard of (yet).

Understand the owner not being available, but want to chime in and say that the real world effect on my company is significant. We're an interactive video SaaS platform that has essentially lost the ability to provide/guarantee functionality of our core service to clients who are using recent version(s) of Chromium - 45% of our traffic.

Similar  bug 822197 .

I moved the test page to https://mounirlamouri.github.io/sandbox/bugs/821576.html and looked at different browsers and the results seems to be:
- Firefox: does show the button while in fullscreen;
- Safari: the button click handler does not work while in fullscreen (or in-page);
- Edge: the button does not *show* while in fullscreen (note: tested using browserstack so I may have missed something)

It seems to me that this is a Chrome-only regression for something that only Chrome used to allow. I will keep the RB-Beta label so foolip@ prioritise looking at this. Unless the spec says otherwise, we might want to consider doing what Firefox does and not show the button when the video is fullscreen.

Hi - 

Was Safari tested in Browserstack as well? If so, can I ask that this be tested in the actual browser? The button does work as expected for me when tested in fullscreen in Safari. I've attached another video. You can see the 'hi' count in the log increment after clicking the button in fullscreen.

Would it be possible to get a link to or some other idea of what the spec is you're working to? Doing what Firefox does would be, really, really bad for us - it wouldn't solve this issue, and would create another one. Ideally, we'd like to see this work how it used to and how it works in Safari, unless there's a reason for it not to. I'm trying to get an idea of what that reason could be. 

Thanks again for your attention to this, we appreciate it.

Deleted: Safari Button Test.zip 20.7 MB

Safari Button Test.zip 20.7 MB Download

Since M66 Beta has also rolled out, moving this to RB-Stable. 

Removing "M-65" per comment #10.

I have the same issue. I had created this codepen before i found this issue.
https://codepen.io/bertyhell/pen/ZxLNeg

Steps:
* play the video
* click the toggle fullscreen button to make the video fullscreen
* click the toggle fullscreen button again

expected result: the video exists from fullscreen mode

current behavior: Nothing happens

Video of the issue tested on chrome 63 (working) and tested on chrome 65 (broken)
http://www.youtube.com/watch?v=k0aOZN0BHXQ

Friendly ping to get an update on this issue as it is marked as release block stable.

Thanks..!

Just a heads up, M66 Stable cut is on April 12th, 10 days away. This issue is marked as RB-Stable for 66. Please make sure to address this issue prior to stable cut. Thanks! 

foolip@, any update on this?

This is the same as  issue 810308  which I closed as WontFix, see comment #9 for an explanation. With  issue 240576  fixed the button will also not be visible.

With the fullscreen button in <video controls> there won't be any way to make anything overlap the video. To do that, it'll be necessary to use custom controls for the video and make the fullscreen button fullscreen the parent element instead.

Sorry that this is not an entirely satisfactory workaround, but at least I can't see a reasonable path forward for fullscreen where we keep the z-index workaround working *and* where it's possible to interact with the things that are made visible by z-index. That's because it would require reverting https://chromium.googlesource.com/chromium/src/+/17dd72fb55aaa071bf1077a02e45b9f2f44d1ed2 and using some very different logic for determining for what part of the page screenreaders read out when in fullscreen, something that depends on the layout.

Please let me know if this will affect already deployed sites and no workaround can be found.

I don't understand how this bug is in WontFix state
Solving some bug in Android for accessibility doesn't need to effect desktop users of chrome.
Not allowing this functionality harms a lot of companies that provide platforms for video annotation and quizzes etc, It hurts these companies and their clients.
The workaround is not a wide solution for all the types of video players.

This issue is simply a huge irresponsible from the chrome developers part !

Thank you for the explanation of the won't fix status.

We were using the z-index hack to show custom video controls in fullscreen. Kt sounds like the workaround that you suggest should work for that.

For now we just show the native video controls in fullscreen mode. Which isn't a big deal since it is the same behavior as all other browsers.