@up: nope, it didn't work for me

#61  It didn't work for me either.

Same issue here. I'm using Windows 8.1 x64, 3 monitors, newest Nvidia drivers, Chrome 51.0.2704.103 (64-bit), fresh (!!) system install and the task bar (windows start bar?) won't hide when I go fullscreen on one of youtube (or any video) movie on any of side screens. 
Attached screenshot describes the problem better.

Deleted: PROBLEM.png 4.6 MB

	PROBLEM.png 4.6 MB View Download

Is there a reason why Google is waiting until the end of July to release a fix for a problem that's affecting such a large amount of users and has existed since April? Considering how many people posted on this thread, I can only imagine there are hundreds more that didn't bother taking the time to search for a bug thread and just switched browsers.

#75: This is the standard Chrome release policy. We cut the development branch every 6 weeks, and then it goes through 7-8 weeks of solid testing on the beta branch before going to stable. The downside of this is that if a bug does make it through to stable, it can take up to 3 months for it to be fixed in stable.

If a bug is considered serious enough (like a security vulnerability), we can patch it much faster, but we don't do that for non-serious bugs as it bypasses the normal testing process (we want our fixes to go through the full testing cycle to make sure they don't introduce even worse bugs). This bug is a minor nuisance, certainly not meeting the bar to be rushed through to release.

#76: Last update didn't fix it, so I guess the policy is another 3 months with this bug?... I must say, I am a bigger fan of the JDI approach!

#78 "Last update didn't fix it" ... which update is that? If you want to tell us something is not working, you need to give the version number (found in chrome://chrome) so we know whether our fix actually didn't work, or whether you just haven't updated to a version new enough to contain the fix.

#78 It's fixed for me in the latest chrome beta [52.0.2743.60 beta-m (64-bit)] are you sure your trying the beta?

Just updated to Stable 52.0.2743.82 m (64-bit).

Issue is still present.

After further testing I've found that the issue seems to be fixed for any windows fullscreened on my secondary monitor. 
But it does remains for any windows on my primary monitor:

It no longer triggers when I click on the taskbar on my secondary monitor nor when I click on any other window (neither Chrome nor another program). It only triggers when I click on the desktop of the secondary monitor.

Should I open another bug report for this? Is this one considered closed?

Just checked and the same is for me. Checked with Version 52.0.2743.82 beta-m (64-bit) and the latest stable.

ah true, I only did test it on the second monitor last time.

I see the same behavior with Internet Explorer as well. Please verify and update here.

Thanks

Yup, I can confirm that the same behaviour exists with IE.
However; I decided to take one for the team and tested Edge (*shudder*) and the issue isn't present there. Neither monitor produces the bug.

My problem in Chrome is now fixed. Was about time.

Problem not fixed. The main monitor of a 3 monitor setup is still showing the taskbar above fullscreen flash videos.

I was able to fix this problem by going following these steps:
1) Go to the sandwich bars in the top right > Settings > About 
2) Chrome should now start to update

After the update I had no problems with the taskbar showing up on fullscreen and going to my second or third monitor. 

Fixed for me in Version 52.0.2743.82 m

Well the problem was fixed for me, but now it is back with version 53.0.2785.34 beta-m (64-bit).

Problem still here! 

Youtube, Streams, everything is not fullscreen - it works only if i go into a video after restart my pc. 

Idont want to use firefox, but its the only option for movies i found so far. 

PLS omg fix it i hate this lagging fox so much 

I'm seeing more reports of this (from today):
https://www.reddit.com/r/chrome/comments/4xrxtl/fullscreen_isnt_working_properly/

No version given but presumably 52 (which has been stable for awhile). I think we still have this problem. Reopening.

 Issue 591278  has been merged into this issue.

For me 52 works as expected (when it comes to taskbar showing!).
I have not tried 53 beta.
According to the screenshot of the reddit thread there the problem is not that the taskboar shows but that the whole browser shows! That sometimes happens to me, too.
That is the one tracked in  Issue 605412  and should be fixed in 53 according to the comments. Or am I wrong with this?

I'm on 52.0.2743.116 m (64-bit) and I still have the issue, fullscreen is just not fullscreen.

#97
I think there are some issues mixed here.
This issue is about Taskbar showing over fullscreened video.
(As showed in the screenshot of Comment #9)
The rest of the browser window does switch to fullscreen.
Is the issue you have that the Taskbar is showing over a fullscreened video or that fullscreen is not hiding the browser UI?
That seem to be two seperate issues in my opinion.
While the Taskbar not hiding should be fixed in 52 the fullscreen issue (which for me appears randomly) should be fixed with 53 according to  Issue 605412 

I have had the issue where fullscreening a Youtube video makes the video only fill the browser's viewport, not making it true fullscreen. This has happened only once so far, though.

Does not seem like a blink issue per the commits above. Removing blink component.

Bug is still present in canary (version 54.0.2840.0 canary (64-bit)).

So, when can we expect this issue to be fixed?

Deleted: bug.jpg 446 KB

	bug.jpg 446 KB View Download

Just got 53. The same problem persists, where the issue is fixed in every single permutation except for when the fullscreened video is on the primary monitor and you click the desktop on the secondary monitor.

Also JESUS is 53 UGLY!

Noticed something: If I click on another program or on the activity bar at the bottom of the screen BEFORE I click on the desktop the bug doesn't trigger.

Only one display here and the Windows 10 taskbar always overlaps Chrome in fulscreen. It's very annoying as it covers YouTube controls. Chrome 53 Stable.

Similar to the last comment, I only have one display and the same behaviour is happening. Windows 10, Chrome 52.0.2743.116 m.

Deleted: Screenshot (4).png 2.0 MB

	Screenshot (4).png 2.0 MB View Download

Still the same problem....It's very annoying...I'm on Windows 10, Anniversary Update and my Google Chrome's version is 53.0.2785.116 m

Deleted: Google Chrome problem.png 1.8 MB

	Google Chrome problem.png 1.8 MB View Download

Everyone here thinks they are helping by saying they have the problem lol... just wait for someone to reply you ignorant people

Knowing how many are affected and how the bug materializes is invaluable information. Such as whether or not the bug is still present in certain versions of Chrome. And many comments were submitted weeks in between.

Fixed in both Chrome and IE by enabling Aero and Transparency in Windows 7 64 bit. 

Still the same problem....It's very annoying...I'm on Windows 10, Anniversary Update and my Google Chrome's version is 53.0.2785.143 m

Deleted: WhatTheFUUUCCKKK.PNG 434 KB

	WhatTheFUUUCCKKK.PNG 434 KB View Download

I don't believe this is an issue with Chrome, but an issue with windows taskbar. Stopping the explorer.exe process and restarting it fixes 100% of the time.

I agree on it being a problem on Windows' side. I observe the same behaviour in both Chrome's 'Full Screen', as in various games that have a 'Windows Fullscreen' mode, which is basically the same as Chrome's 'Fullscreen' mode.

I think that's just because Youtube's fullscreen mode is just another version of Chrome's fullscreen mode. Ever since YT switched to HTML5 instead of Flash it has utilised Chrome's F11 mode.
And as far as I know the issue started in the first place bacause Chrome starting removing 1 row of pixels from fullscreened windows because of... issues with something, don't rememeber what.

The issue occurs with DisplayFusion's taskbar as well; according to them it is occurring on the Chrome side: https://www.displayfusion.com/Discussions/View/windows-10-google-chrome-youtube-fullscreen/?ID=dc779b8b-bcc5-4f2a-b306-592345a99588#7

Updated to 54.0.2840.59 m (64-bit), issue is still present.

Same as before: it's fixed in general but if I fullscreen a video on the primary monitor, and then click the dektop on the secondary monitor, the bug will trigger.

Deleted: issue.png 1.5 MB

	issue.png 1.5 MB View Download

In chrome 54 this bug is resolved on my Linux Mint system.

Version 54.0.2840.71 m still occurring on a single monitor system Windows 10.

Restarting Windows Explorer using taskman seems to temporarily resolve the issue.

Versie 54.0.2840.99 m (64-bit) on Windows 10

Deleted: wtf youtube.PNG 1.5 MB

	wtf youtube.PNG 1.5 MB View Download

I'm on Windows 7 x64 with Chrome BETA and it was never fixed for me. I rarely use dual screen mode I work mostly on my laptop's screen.

Chrome 54.0.2840.99 m on Windows 7 Pro - the problem is present for many weeks. Chrome F11 is not hiding Windows toolbar either.

Problem still persists months later.  Win10 and 54.0.2840.99

Dave

I just started having this problem but I only have one monitor.

The title is misleading because it's happening on single screen setup too.
I wonder how complicated this issue must be that they can't fix it since April. 

It's not like they didn't have time. I think they just don't care.

"It's not like they didn't have time." <-- I think the term you're looking
for is "It's low priority", evidenced by Priority being set to "1". This
bug is a problem for me, too.. but it doesn't completely break usability.
It's mostly an annoyance. If you have a use-case where it's a real problem
then you should submit that information and try to get the priority
upgraded. The Chromium project is made up of a lot of volunteers; please
try to keep a respectful tone.

The Chromium Project is basically a Google Chrome testing area. Everyone knows that Chrome is based on what's happening here so it's not like those "volunteers" are working here for free, at least not all of them. Please don't try to paint Chromium as this "wonderful project developed by people around the world, united to make internet browsing experience even better". Keep marketing out of it.

I also get this is a low priority and mostly an annoyance but you can't keep ignoring it and hope that people forget about it. In your opinion. How long should it take to fix a low-priority bug? More than 8 months? More than a year maybe? 

It would be great if the developers would surprised us with a Christmas gift and raised the priority-level of this bug. I'm trying to be a realist here and I'm not gonna even ask for a fix for this issue. At least not this year.

I didn't paint it as anything. I only asked that you please don't make
disparaging remarks about volunteers. You're free to fix the bug yourself,
I'm sure plenty of people would appreciate that.

"How long should it take to fix a low-priority bug? More than 8 months? More than a year maybe?"

Here's a "critical" severity ticket in WordPress that has been open for 8 years: https://core.trac.wordpress.org/ticket/8592

And here's a "normal" priority UI bug in FileZilla that was reported over 9 years ago: https://trac.filezilla-project.org/ticket/2905

I could add many examples, but Chromium is hardly alone in the OSS world as far as neglecting to fix long-standing "trivial" bugs.

I was able to fix this bug by unchecking "Lock the taskbar". The option should appear if you right click on your taskbar. If the setting doesn't show up, you can find it in taskbar settings via the search function.

Priority 1 is actually the highest priority a bug can have (outside of critical stability/security issues that can seriously compromise users). The problem is I don't think we have any reliable way to repro this issue which makes it very hard to fix.

This isn't about "we don't care"; this is about we're not really sure what we can do or even if it's our problem (since it seems more like a Windows problem than a Chrome problem).

https://www.youtube.com/watch?v=Hu-JBDGGnSU

hahaha

I don't think that's the fix but thanks anyway, I guess.

"This isn't about "we don't care"; this is about we're not really sure what we can do or even if it's our problem (since it seems more like a Windows problem than a Chrome problem)."

For me it happens only on Chrome and on Win7, Win8.1 and Win10. I don't use older systems or Linux. Also I can't imagine that no one on the Chromium team experienced this bug. I don't know what more information do you require to find the cause but I think if we get more instructions from the Chromium Team I think we can help you better. 

It's just hard to provide any useful feedback if we don't know where to look.

#132: Thanks for the helpful video, that adds some context (though obviously not a proper fix).

#134: I understand the frustration. I don't know what more information we can get from you that will help. From my understanding, a relatively small number of people are getting this and it's flaky (doesn't happen always). The fact that restarting Windows Explorer fixes it suggests that it is a bug in Windows Explorer, not Chrome. It's possible that there is other software on the affected systems that's causing it.

You say Win7, Win8.1 and Win10. Do you have three separate machines all experiencing this same behaviour, with the different versions of Windows? Or have you just upgraded the same machine through those versions? If the former, do you have any other software that you've installed common to all three machines?

Yes, I'm having three separate computers. Two of them are running Win7 and one Win10 but before it also run Win7 and Win8.1 for a few months. All three of them are experiencing this issue.

All three on them are running similar or the same software package. If you'd like I can provide you with installed software list, just let me know.

I'm having same problem on Surface 4 Pro running Windows 10 Enterprise (vanilla, installed clean). Same issues, restarting Windows Explorer also helps. Problem affects only Chrome - full screen in other applications (like media players) works fine.

I can provide installed software list if needed too. Hardware and drivers should be easy to repeat - it's the same for every Surface.

POTENTIAL SOLUTION: Hey guys I noticed a lot of people are having issues with this problem. I had it a while ago and found that just clearing your cache and cookies can sometimes fix the problem, but it's annoying because you having to reenter all of you data for usernames and passwords. So far it's the only thing I've found to have any kind of measure of success. Hope this helps! 

I don't think it's even close the a solution.
It's more of a workaround rather then solution.

It may be not a Chrome problem. For me the same thing happens with Media Player Classic HC @ fullscreen just as with Chrome. Don't know what triggers it.

That's definitely interesting. I'm also using MPC-HC and I never encountered issues with fullscreen. I'm using the latest nightly delivered with K-Lite Codec Pack 10.7.5 (I think). Can you tell us which version of MPC-HC are you running and if you downloaded it as standalone program or did it came with some codec pack?

Also is resetting it to default settings resolves the problem with fullscreen? Make sure to make a backup of your current settings from option menu.

I know it's not MPC-HC bugtrack but Chromium developers asked previously if anyone is experiencing the same issue with other apps.

I see it on my second display, which is using DisplayFusion's taskbar
instead of the native Windows task bar. It does NOT occur with MPC-HC for
me, only with Chrome. The Binary Fortress team seems to feel they have a
handle on the cause and that it's to do with Chrome:
https://www.displayfusion.com/Discussions/View/multi-monitor-task-bar-showing-in-full-screen/?ID=cc754595-54b9-452b-8d77-db1d7c0d2b0a

MPC info for comparison:

MPC-HC (64-bit)
---------------

Build information:
    Version:            1.7.10 (d911f14)
    Compiler:           MSVC 2013 Update 5
    Build date:         Nov 14 2015 18:25:24

LAV Filters:
    LAV Splitter:       0.66.0.0
    LAV Video:          0.66.0.0
    LAV Audio:          0.66.0.0
    FFmpeg compiler:    MinGW-w64 GCC 4.9.2

Operating system:
    Name:               Windows NT 10.0 (build 10586)
    Version:            10.0 (64-bit)

Hardware:
    CPU:                Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
    GPU1:               NVIDIA GeForce GTX 680 (driver version:
10.18.13.6869)
    GPU2:               NVIDIA GeForce GTX 680 (driver version:
10.18.13.6869)

#142: Thanks for the link to that discussion.

Note that this discussion is from April 2016 on Chrome 50. Ananta's fix (r394000) went out in Chrome 52 AFAIK, so the situation has changed somewhat. (The discussion specifically mentions the 1px hack that was put in Chrome 50. The hack wasn't removed exactly but its behaviour has been changed.)

Perhaps ananta@ can comment further on this.

Still the same problem....It's very annoying...I'm on Windows 10, Anniversary Update and my Google Chrome's version is 556.0.2924.76 (64-bit)

Deleted: youtube bug chrome.PNG 2.5 MB

	youtube bug chrome.PNG 2.5 MB View Download

**************WORK-AROUND****************

@ananta@chromium.org
@engedy@chromium.org

Non-Google SW Support here.

What's good guys and girls?

So the work-around/solution is really simple.
I am not sure what the root cause of the issue is, but it seems related to only Windows 10 machines.
The way to fix this is to lock your device and then unlock it again.
Restarting Chrome also helps, but with locking you don't have to go to history and reproduce the state of your pages.
Hope Google staff sees this.

Cheers!

this happened with me to, i just restarted my computer and it was fixed ^w^

It's starting to looks like it's not Chrome problem at the end - but Windows. Same thing happened to Remote Desktop Client running in full screen. W10 Ent 14393. Will investigate when it will happen again.

I made a batch to pskill explorer and start it again - quick way to fix it.

Same problem. Single monitor, Win 7, Chrome 55.0.2883.103
No problem on old 50.0.2661.102

I have the same problem on latest stable Chrome (56.0.2924.87 x64). I have a single 1080p monitor, AMD GPU and Win7 x64 SP1, but here's the catch - the taskbar sometimes remains, and sometimes goes away as it should - it depends whether I mess around with menus, windows or other screen elements. So the problem is intermittent. The only thing is, I don't recall it ever happened before (prior to version 56).

i have same issue on my single moniter setup running on win 7x64 profesional and gtx 750 ti

Deleted: fffffffffffffffffffffffffffffffffffffff.png 2.8 MB

	fffffffffffffffffffffffffffffffffffffff.png 2.8 MB View Download

This issue is still present on my Win7 Chrome (56.0.2924.87 (64-bit))

It's a minor but annoying issue, can't believe it's still not totally gone.

Hey guys! Sorry for quick double post, I found a fix for my problem for Chrome 56.0.2924.87 (64-bit) on Win7, just relock your task bar. (Right click on taskbar, and uncheck and check it if it's checked or just check it if it's not!)

it even appears when pressing f11 in chrome only

Deleted: Screenshot (456).png 340 KB

	Screenshot (456).png 340 KB View Download

Version 57.0.2987.110 (64-bit) Windows 10 v1607 b14393.693; happens regardless of "Show taskbar on multiple monitors" or whether the taskbar is locked. Haven't had an issue with 56.

I have only one screen and this happens from time to time at least for a year, as far as I remember.
Btw, if I close something on a taskbar by right-click on program -> "Close" then taskbar disappears and everything works good. 

Deleted: 1.jpg 364 KB

	1.jpg 364 KB View Download

same issue, windows 10, problem only happens with chrome 

Deleted: Captura de Tela (38).png 1.2 MB

	Captura de Tela (38).png 1.2 MB View Download

Not fixed.
I noticed that when you use ALT+TAB while in full screen the taskbar disappears.

June 29, 2017, Last week or so ago, the problem where the task bar will not disappear on Chrome, on any website on full screen, on my Toshiba laptop (Windows 10), suddenly started. (The taskbar remains on my desktop as usual.) I've had no similar problems, nor have I made any significant changes or control/setting changes, except for the automatic updates for all systems,  to my laptop in the last couple years of having it. I've tried various simple things to resolve the problem, but was unsuccessful. (E.g. I tried some suggestions from other commenters here, but did little else, as I'm fairly ignorant on such matters) It's a very annoying and frustrating problem. It seems that this problem has been unresolved for quite some time now. I am wondering what the progress is towards a resolution ? Or are their any new suggestions that I might have missed to help resolve the problem ? I would much appreciate any help on this.

Hey try this (i know it's for FF but it worked for me for all fullscreen softwares):
Right-click on your Firefox icon   (not the one on your desktop).
If it's not on your desktop,   find it in the   Mozilla Firefox program folder.
After right-clicking,   select   'Properties',   then the 'Compatibility'tab,   and then check the box that says:
'Disable display scaling on high   DPI   settings'.
Also:   make sure that in   'Properties'  the taskbar is not set to be visible all the time.

source : https://support.mozilla.org/fr/questions/1141940 

Why would I want to do this?
Why would I want to apply some kind of workaround to fix the issue they created and they should have fixed already?

Thanks for the tip but I'm not going to use it.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9c35b80be7b82051abec46fabdcdef6be4b214a2

commit 9c35b80be7b82051abec46fabdcdef6be4b214a2
Author: ananta <ananta@chromium.org>
Date: Thu Jul 06 22:10:49 2017

Another attempt at fixing the fullscreen issues with Chrome.

The ITaskbarList2 shell interface provides a way to mark a window as fullscreen. As per
msdn https://msdn.microsoft.com/en-us/library/bb774640(v=VS.85).aspx the MarkFullscreenWindow()
method on this interface when called for a fullscreen window ensures that the shell moves the taskbar
to the bottom of the ZOrder when the window is active. When the window is not fullscreen, it fallsback
to its heuristics which include looking at the styles of the window, whether it is maximized etc, which
sadly means that a non fullscreen window could be treated as a fullscreen window.

In any case this should hopefully help us make incremental progress on this issue which has
been affecting users for a long time.

BUG=604359

Review-Url: https://codereview.chromium.org/2972963004
Cr-Commit-Position: refs/heads/master@{#484753}

[modify] https://crrev.com/9c35b80be7b82051abec46fabdcdef6be4b214a2/ui/views/win/fullscreen_handler.cc
[modify] https://crrev.com/9c35b80be7b82051abec46fabdcdef6be4b214a2/ui/views/win/fullscreen_handler.h

Windows 10 64-bit
Chrome Canary 64-bit Version 61.0.3152.0
The issue is only affecting my second monitor. Screenshots attached.

Deleted: monitor2.png 674 KB

	monitor2.png 674 KB View Download

I'm still having this problem on Windows 7.

Why is this still unsolved? How do I revert that silly "1 pixel higher" workaround that's present? It never did me any good.

Everyone is still having this issue. It's still not fixed and it's not looking like it's going to be fixed in the near feature. The lack of responses or updates from devs speaks loudly about the progress.

I don't think you can "revert" the workaround on your own without building the Chromium browser yourself without the commit in question. I believe it requires input from developers to get rid of it in Chrome. 

I think I've found an easy solution:

1. Make the video full screen.
2. In the task bar below, right click on the chrome tab that is playing the video so that a menu pops up.
3. Left click on the video in the background now (outside the menu) and the task bar should be gone now. Works for me everytime.

Windows 10 64-bit
Google Chrome 64-bit Version 61.0.3163.79
The issue is only affecting my second monitor. Screenshots attached.

Deleted: Youtube fullscreen bug.PNG 2.0 MB

	Youtube fullscreen bug.PNG 2.0 MB View Download

Data point here: I've only experienced this bug in Chrome a handful of times in the past few years since it was reported. Yesterday I experienced it in a full-screen game (NOT CHROME). Exact same bug: the taskbar was stuck open above the full-screen game, even if I switch back and forth it will always remain on top. See screenshot.

This leads me to believe that it is not a Chrome issue, but just an issue with Windows that happens every so often. We just see it more on Chrome because Chrome tends to enter and exit fullscreen more than other apps.

Another note: This bug is 100% reproducible if you have an always-on-top window on screen. Seems like a deliberate design decision in Windows that if there is an always-on-top window open, then the taskbar is always shown even if the user is in a full-screen app. So the cause of this bug *might* be that some random invisible window has made itself always-on-top and while you can't see it, it's triggering this same behaviour.

We can work around it but I truly think this is a bug (or mis-feature) with the operating system and these complaints need to be directed at Microsoft.

Deleted: game-taskbar-bug.jpg 651 KB

	game-taskbar-bug.jpg 651 KB View Download

Unassigning all bugs for ananta@chromium.org

It's worth mentioning this may be a Windows bug. When this is happening, try moving your mouse over a taskbar button (one of the window "tabs" in the taskbar) and then off again. Does the highlight "stick"? That's a bug that's been around since Vista, and yes it's extremely stupid that it hasn't been fixed. When that bug occurs, borderless fullscreen windows won't properly hide the taskbar (it's essentially stuck in a weird state). The way to fix it easily (without having to restart explorer or the computer) is to right click one of the taskbar buttons so the context menu appears. If that doesn't fix it, shift-right click (but you have to find a window that has an old-style context menu; if nothing appears when you shift-right click, it won't fix anything).