I confirm the bug. I actually have the same problem with Safari beta.

Following the steps above, in Windows Vista, sometimes I get the same result,
sometimes the taskbar pops up but then immediately disappears.  The later result only
happens if (but doesn't always happen when) the mouse is moved to the bottom of the
screen very quickly (like < 1s).

Confirmed in Windows Vista with an Acer Aspire 5610Z.  Task bar does not come up at 
all with window maximized; it comes up BEHIND the Chrome window when it is not 
maximized.

Confirmed in Windows XP SP3 on a Dell Vostro 1500.
On my main computer with a dual monitor setup, i can get the taskbar to pop up on the 
main monitor, however on the second monitor i experience this problem  

I'm on my pc at work running Windows XP SP3 and I can get the taskbar to pop-up like 
it normally even when Chrome is running maxed.

Confirmed on my XP SP3 dual monitor. Chrome maximized hides the task bar only in the 
second monitor.

I can also confirm this bug with chrome 0.2.149.27 on vista home premium

I am using Vista Home Premium with SP1 on HP Pavillion dv6500 Notebook. The issue 
will only appearing when auto hide enabled after opening chromium and it works as 
expected when once you minimized and used hided task bar it appears then after with 
chromium also

Confirmed and it is very anoying, i have to use the "windows key" everytime i want to 
get my taskbar.

confirmed on 2 vista machine
1) Vista Ultimate (Dual Screen)
2) Toshiba R400, Vista Business

I confirmed. It's very uncomfortable. My machine is Lenovo R61i, and uses Vista 
Ultimate.

I confirm this issue but I'm using RocketDock instead of the windows taskbar.

RocketDock is supposed to stay always on top, but not enough to beat the Chrome-on-
Top :/

I confirm this issue using a DELL Dimension with Vista Home.  Frustrating.

Same problem here...

Yes, there is same problem. So annoying...

Toshiba A200, Vista Home Premium SP1.

Confirmed as an issue on a Dell Dimension running Vista Home.

(No comment was entered for this change.)

I have the same problem - Vista Ultimate on a Dell Inspiron 1501 - need to use 
windows key to pop up taskbar.

I have also noticed that when alert comes up in the taskbar - i.e., an IM window is 
updated - the taskbar comes up but does not display until you unfocus the Chrome 
window.

F11 is not working to Full Size Screen.
 

"F11 is not working to Full Size Screen."

Same here, but this should be filed under the proper report (or a new one if there 
isn't one existing).  F11 is a different type of command than maximizing the screen.

The same problem happens also with the "onscreen" keyboard when you have a tablet PC.

I can also confirm on Vista SP1 (x86).  Chrome also seems to misbehave when always-
on-top windows (such as Trillian message windows) are placed over the browser window.  
Many times Chrome will simply appear over them even though they are set to always-on-
top, or will appear over the window when it has focus, then operate properly when it 
loses focus.

Same problem.

I have Vista SP1 on an x86 system, and this happens to me.  Happened before I 
installed SP1 as well (just recently installed it).

The same situation here on Vista SP1. I need to press "windows + T" keys get a 
taskbar visible.

Confirmed on vista SP1 (Dutch version)!

I am running Vista Ultimate SP one.  I have my task bar (on auto hide)on the top of 
my screen and more than 75% of the time when chrome is maximized, it takes precedence 
over the task bar. 

Confirmed on XP 32 SP3

This is IMO the most annoying problem in the Chromium so far... Is it going to be 
fixed in 0.3?

Vista Business 32bit, same problem here. 

[magic_browzR] XP Pro SP3 32-bit confirmed here.

(No comment was entered for this change.)

also confirmed here on vista sp1

I confirm this on XP Pro SP3. It also ignores Winamp auto-hide. A very annoying bug, 
especially if you have a large taskbar. It also messes with my Messenger, as I often 
miss messages since MSN apparently gets Chrome as a fullscreen window.

Just tested on 0.3.154.0, still has the same problem.

Chrome Covering Taskbar.WMV 2.0 MB   Download

hey everyone, dont know if this is the right forum to put this in but not being able 
to use taskbar authide and chrome together has really been bothering me, and i think 
this will help a lot of people in a similar situation. if you download desktopcoral, 
place the dock at the bottom, and set the dock height to 1, taskbar autohide and 
chrome can be used together. desktopcoral essentially reframes the limits of a 
maximized window on one side, and using it like this keeps chrome from taking up the 
tiny bit of an autohidden toolbar at the bottom of the screen. enjoy.

Make this the main tracking bug or  issue 200  instead?

I have the same problem. Using latest Chrome as of 10/16/2008, Vista SP1

Confirmed on my Vista SP1 Buisnes.

Ditto, same here Vista Home SP1. Very annoying!

(No comment was entered for this change.)

(No comment was entered for this change.)

This problem has been fixed in the hourly builds:
http://build.chromium.org/buildbot/continuous/LATEST/

Just tried but the problem still persist for me.

I used the mini_installer.exe

same problem, hope for fixing

I found it works when I am only using my laptops screen, but when I am also using
another external screen, I cant un-hide the sidebar or taskbar.

I use only the laptop screen. It's a Vista tablet, if that matters.

However, it works fine on another tablet, though that is a XP. But according to some 
of the above comments both XP and Vista is affected.

confirmed with Windows Vista Ultimate on my Dell Precision Workstation 490

Problem persists after installing Chromium latest

"Problem persists after installing Chromium latest"
I second that

Confirmed Bug. Windows Vista Business Edition on Toshiba Satellite A215.

Confirmed on hp dv6258se notebook running Windows Vista Ultimate and Chrome 
0.3.154.9. Task bar refuses to come up with Chrome maximized bumping the bottom of 
the screen with the cursor. When not maximized, the task bar pops up behind the 
Chrome window.

Fixed in trunk r4825.

Assigning to mal if this needs to be part of 1.0

Merged into the release branch at r4859. Will be released in 154.11 and later.

Build: 0.3.154.12 (Official Build 4978)
Opps, I can still reproduce this bug with following tricky repro steps :)

-Launch Chorme browser window 'n' maximize it.
-Right click on Taskbar and select properities.
-Check "Auto-hide" the taskbar to ON and apply changes
-Click on Chrome Button on Taskbar.
-Mouse hover over the taskbar position. 
You don't see the taskbar pops up.
I can reproduce this consistenly on Vista Enterprise SP1.

Please note, once I un-maximise and maximize Chrome window, then I can't reproduce 
the issue. 
-Venkat.

For me, it looks like new issue with those repro steps (?).

It happens for me on both Vista/XP SP3 consistently.

This is really a new bug (task bar autohide doesn't work while Chrome is maximized 
IFF you enable it when Chrome is maximized).

I say this is not worth fixing. What do you think Amit?

Yeah this is a temporary fix anyway, this should be fixed when we have a proper fix 
for the original issue.

def needs to be fixed, very annoying, I love chrome, but this and the pdf problem is 
really putting me off

Indeed, definitely needs to be fixed. If there is a reason why I will stop using 
Chrome it will be because of this. This a small but nevertheless very annoying 
problem.

Is this not yet in the main? Just tried the build at http://build.chromium.org/buildbot/continuous/LATEST/ but the problem persists.

Confirmed (partially) fixed on 0.4.154.18

Taskbar now stays at front after Chrome is "maximized"... However Chrome is not 
really "maximized", there are some blank spaces to the bottom and to the right...

Normal...?

Yeah, that's the expected behavior. Well, this is a quick (and less risky) work 
around for this issue. Once we enable new frames we should have a better solution for 
this issue.

Now its been over 2 months since the first discover about this bug. Any fix on the 
way?!

A work around for task bar auto-hide is already part of the latest builds (might take 
some time to appear in the Beta builds though). 

This issue now happens only (once) when the task bar auto-hide is enabled while 
Chrome is maximized.

Better fix for this will be available in future.

Crikker: The dev-channel build 0.4.154.18 has the partial fix implemented.

amit: Any timeframe that the "better fix" will be available...? I'm asking because this 
partial fix doesn't seem (to me) to be good enough to be included in the Beta builds.

If it's so, "when the 'better fix' will be available" warrants more attention then.

With respect and thanks for your work, I would rather run a Beta build than a dev-build, 
the latter being less stable.

Dev builds are only meant for the audience that want a peek at the latest features 
but can tolerate instability (like testers and web developers). Beta builds are are 
for normal everyday usage so you are right in staying with the beta build.

About the time line for better fix: it depends on a number of factors and can't make 
a good guess at this time.

Looks like this is a dead topic - I would add that sometimes the audience turns to 
dev builds because there are faults in the beta builds that we see as intolerable 
instability such as not being able to access the taskbar.

Update: The partial fix has been pushed to the latest beta build (0.4.154.25) as far 
as I can tell.

The taskbar issue appears to be worked around in 0.4.154.25 but now there is a large 
bottom border on the Chrome window when maximized. It is double the size of the 
normal border (see red oval in attachment "Chrome maximized.jpg").

	Chrome maximized.jpg 112 KB   View   Download

It is also important to note that the "Taskbar autohide doesn't work if you enable it 
while Chrome is maximized" is not the only issue... this problem occurs anytime 
Chrome is maximized.

To Cummings.William: The large bottom border is supposed to be there with the partial 
fix. The better/complete fix is not available yet.

Besides, can you elaborate what you said in comment #71...?

In comment 71, I meant to make sure the development team knows the issue occurs 
anytime autohide is enabled; not just when it is enabled while Chrome is running as 
the bug statement implies. Before the work around was introduced, my taskbar was 
buried anytime Chrome was maximized.

 Issue 1595  has been merged into this issue.

I Confirm. Windows XP sp3 and chrome 2.0.156.1

Same here! Vista Home P with chrome 2.0.156.1 on Toshiba X200.

 Issue 6190  has been merged into this issue.

Same issue to report here with XP SP2 and Chrome 2.0.156.1.

 Issue 6411  has been merged into this issue.

It seems a tiny bit fixed for me on 2.0.5.170.  Two pages I have spun off to
'application shortcuts' I can get to work with auto-hide taskbar - on one (a Google
Docs spreadsheet) by making that chrome window smaller, clicking another window,
clicking that chrome window again, moving the mouse to where it triggers the taskbar,
then maximising the chrome window again and the auto-hide taskbar works fine after
that.  On the other (BBC iPlayer) it works fine from the start.  But on the standard
Google Chrome app itself I still haven't been able to coax the auto-hidden taskbar to
unhide itself.

Confirmed with Windows 7 and Chrome 2.0.157.0

I just filed a bug for this too... I also have the same problem with Songbird... 
XPSP3

As a follow-up to my comment 80 about the application shortcuts for which the either
the auto-hide taskbar unhide worked or could be made to work with some fiddling
about, neither are reproduceable by me today, they both completely fail to play nice
with that auto-hide taskbar like the main Chrome app!  Maybe if I fiddled about
turning the taskbar auto-hide off and on... no, just tried that, didn't help.  Maybe
if I closed Chrome and then... no, I'm not trying that, I could spend forever trying
to reproduce exactly the combination of things that got it slightly working
yesterday!  And I forgot to mention, I'm on XP Pro SP3.

 Issue 6453  has been merged into this issue.

Confirmed on 2.0.157.2 with XP Pro SP3

Confirmed on  2.0.157.2 with Windows XP Home SP3.

 Issue 6623  has been merged into this issue.

 Issue 6706  has been merged into this issue.

 Issue 200  has been merged into this issue.

this does happen sometimes, but not always.
If you get this problem, just restore and re-maximize the window, and every thing 
shoyld work fine, even with thee window maximized...

Confirmed on 2.0.158.0 with Windows XP Pro SP3.  Unable to reproduce workaround
suggested in comment 91.

Confirmed on 2.0.159.0 with Windows XP Pro SP3.

Confirmed on 2.0.159.0 with XP SP3 and comment 91 doesn't fix it.

Confirmed on XP Tablet PC Edition 2005 Version 2002 SP3
Chrome 2.0.159.0
Definitely the most annoying bug now that virtual mouse scrolling has been fixed 
(thanks!).

Win XP SP3, Chrome 2.0.159.0. I have the same problem with maximalized Chrome. Other 
applications are without problems in the same time, but when Chrome window is activ, 
the taskbar doesnt appear. Its big problem for working with chrome...

Same problem here.

Does anyone know if (and when) this bug is fixed? :)

The 1.0 release used to have this problem until a temporary fix was implemented. See 
comments around #60-#70.

With the 2.0 release, "new window frames on Windows XP and Vista, supporting windows 
cascading and tiling, and other window-management add-in programs." So it seems that 
this problem isn't addressed with the new window frames.

Please, coders, fix it before 2.0 becomes stable and is automatically pushed out. : )

+cc deanm, he has volunteered to investigate. 

Thanks!

 Issue 7510  has been merged into this issue.

I can't reproduce this on my machine, I guess it sounds like mostly a problem on 
Vista.  It will be a ton of work for me to setup a Vista VM, so I'm not sure it's 
logical for me to work on it, sorry.

I confirm the bug on Windows XP, however.

Alright, reproduced it when a different version of trunk (on XP).  Looking at it.

Adding Peter, as he worked on some of the maximization stuff.  It's worth noting that 
I'm running the Classic theme, I didn't try it with the standard XP theme.

I think it's possible we're just over maximizing?  It seems like stable chrome leaves 
2 pixels beneath the scrollbar, where you can access the start menu autohide.

The current trunk code looks like it's on top of those two pixels.

See attached screenshot (stable on left, trunk on right).  I put a piece of the 
scrollbars on top of a black patch, and you can see the additional two pixels.

max.bmp 399 KB   Download

Stable and trunk are hard to compare.  We did everything ourselves in the old frame 
code, including a somewhat broken hack to try and not maximize atop the taskbar (as 
you describe -- somewhat broken because it didn't work right on second monitors, 
etc.).  In the new frame code, Window takes care of maximizing us, and we aren't 
supposed to need this hack anymore.  And indeed, if taskbar auto-hide is already 
enabled when you maximize, it seems to basically work right.  I'm not sure what 
causes this particular bug since AFAIK we aren't doing something special here.

Auto-hiding is not something I really understand, which is bad since I will need to 
for fullscreen mode :(

Hmm, my bug may be a totally different bug then. I have my taskbar /already/ set up
for autohiding on the right. When I (then) launch Chrome, the taskbar does not appear.

I think this is consistent behaviour, but I'm running Ubuntu right now so I can't be
100% certain.

I haven't had a look at the code (yet), but are you guys using GetSystemMetrics (and SM_CYFULLSCREEN in particular)?
http://msdn.microsoft.com/en-us/library/ms724385(VS.85).aspx

Here's some background:

Basic problem here is that chrome top level windows don't have any non-client area 
except borders. When such window is maximized (even using DefWindowProc), the task 
bar performs a check to see if the currently maximized window is a 'full screen' app. 

A 'full screen app' is something that has its entire client area stretched to the 
screen. A normal window usually has some non-client elements like a title bar or menu 
so the client area doesn't stretch the entire screen. Since that's not the case for 
chrome, the taskbar detects that it's a full screen application and hides itself 
behind maximized chrome window. 

Previous fixes have been workarounds to reduce the client area by 1 pixel so that we 
don't get marked as full screen apps. This is done by handling WM_GETMINMAXINFO and 
reducing the size of the client area. However, things work little differently on 
Vista and even if we return the reduced client area, the subsequent handling of 
WM_SYSCOMMAND of SC_MAXIMIZE reverts it. The right thing to do here is probably 
implement WM_SYSCOMMAND for SC_MAXIMIZE. This implementation is non-trivial. 

On vista, I added another hack to reduce the client area by a larger amount so that 
the DefWindowProc of WM_SYSCOMMAND for SC_MAXIMIZE would honor the new size. This 
hack has its own set of drawbacks.

Sounds like it would almost be a good idea to have a pixel or two of non-client area 
at the bottom...

I thought that was exactly what already happens - I posted  issue 200  (merged into
this one), which was about finding a "hole" at the bottom of the screen which would
end up bringing up any windows underneath Chrome if I clicked there. Apologies if
this isn't what you meant.

 Issue 7548  has been merged into this issue.

Confirmed with Windows 7 and Chrome 2.0.160.0

Well, for me it doesnt work with ie7, but it does with chrome :D (1.0.154.48 @ Vista 
with Aero skin)
But, there is a gap (about 5 pixels high) between the bottom of the chrome window and 
the bottom of the screen. It's quite irritating sometimes.

This "gap" that you're talking about is adressed here:

 Issue 5054 : [magic_browzr] Window frame drawn incorrectly

http://code.google.com/p/chromium/issues/detail?id=5054&can=7&sort=-
stars&colspec=ID%20Stars%20Pri%20Area%20Type%20Status%20Summary%20Modified%20Owner

This is a regression we need to fix before a Beta update.

It works on Stable --albeit with a cosmetic hack. We should either fix the core issue 
or put in the same hack we have in 1.0 (a gutter of a few pixels between the 
'maximized' window and the taskbar's edge of the screen).

Unfortunately our stable hack breaks maximizing on multi-monitor systems, which IMO 
is far worse.

Amit and I discussed this a bit and realized that we don't fully understand the 
conditions that trigger taskbar hiding, since WMP seems to be avoiding it even with a 
larger-than-screen client rect.  He's in a better position than I am to figure this 
out.

On 2.0.164.0, Windoze XP SP3 the taskbar hides and then is not visible while Chrome 
maximized. Minimizing Chrome shows that it is there; maybe it is a forward/backward 
issue and not a hiding issue?

Looking at:
1.  http://stackoverflow.com/questions/137005/auto-hide-taskbar-not-appearing-when-
my-application-is-maximized
2.  http://blogs.msdn.com/llobo/archive/2008/02/07/maximizing-borderless-window-
using-sysparameter-values.aspx
3.  http://blogs.msdn.com/llobo/archive/2006/08/01/Maximizing-window-_2800_with-
WindowStyle_3D00_None_2900_-considering-Taskbar.aspx

Goofing with WM_GETMINMAXINFO results as in comment 118 item (3) does not seem to 
help.

Maybe we can use SHAppBarMessage() with ABM_GETSTATE and 
ABM_GETTASKBARPOS/ABM_GETAUTOHIDEBAR to figure out where the taskbar is and just hack 
the work rect based on that.

Yeah, I think we'll have to do that.  http://www.microsoft.com/msj/archive/s274.aspx 
says "The ABN_FULLSCREENAPP notification is sent when a fullscreen application window 
is opened or closed. A window is fullscreen when its client area occupies the entire 
screen. Always-on-top appbars should take themselves out of the topmost z-order so 
that they do not cover the fullscreen window. lParam contains TRUE if a fullscreen 
window is opening and FALSE if one is closing."  It seems like we could probably fake 
a notification of "fullscreen app closing", but hacking the work rect is safer.

Changing owner to Peter.

Patch in review.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=10845 

------------------------------------------------------------------------
r10845 | pkasting@chromium.org | 2009-03-03 16:36:48 -0800 (Tue, 03 Mar 2009) | 12 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/browser_frame.cc?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/browser_frame.h?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/glass_browser_frame_view.cc?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/glass_browser_frame_view.h?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/opaque_browser_frame_view.cc?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/win_util.cc?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/win_util.h?r1=10845&r2=10844
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/window.cc?r1=10845&r2=10844

Make Chromium windows not hide auto-hide taskbars.

There are a few caveats here:

* On Aero glass, if the auto-hide taskbar is at the top of the screen, we get one row of nonclient pixels along the bottom of the screen (not too noticeable for light-colored pages, looks a bit odd with a dark page).  I can't find a way around this.

* Switching between fullscreen and normal mode can leave things a bit confused until you click another app and then reactivate Chromium.  This seems to happen with other applications too (e.g. Firefox fullscreen mode) so I'm not too worried.

* Chromium does not deal well with toggling the taskbar's auto-hide setting (or, I think, its position?) unless you restore and remaximize the window.  I tried to fix this via modified handling of WM_SETTINGCHANGE but only made things worse and so gave up.

BUG=20
Review URL: http://codereview.chromium.org/28338
------------------------------------------------------------------------

The fix I checked in should make Chrome play nicely with autohide taskbars.  Note the 
caveats on the patch: in particular, if you toggle a taskbar between autohide and 
not, you need to resize the Chrome window before it picks the change up.

When will this be implemented?

This change caused  issue 8410 ,  issue 8526 , and (I think)  issue 8511 , so it was backed 
out in r11284 and is thus reopened.

Does not block beta but will block stable (I think).

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=11355 

------------------------------------------------------------------------
r11355 | pkasting@chromium.org | 2009-03-10 12:09:07 -0700 (Tue, 10 Mar 2009) | 7 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/browser_frame.cc?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/browser_frame.h?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/glass_browser_frame_view.cc?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/glass_browser_frame_view.h?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/views/frame/opaque_browser_frame_view.cc?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/win_util.cc?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/win_util.h?r1=11355&r2=11354
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/views/window.cc?r1=11355&r2=11354

Make Chromium windows not hide auto-hide taskbars, take 2.

This is very similar to r10845, but also includes a regression fix for  issue 8410 , where locking and unlocking the screen would cause mispositioning of child content.

BUG=20,8410

Review URL: http://codereview.chromium.org/42027
------------------------------------------------------------------------

Fixed (again) in r11355.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=11416 

------------------------------------------------------------------------
r11416 | mal@chromium.org | 2009-03-10 20:12:28 -0700 (Tue, 10 Mar 2009) | 11 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/browser/views/frame/browser_frame.cc?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/browser/views/frame/browser_frame.h?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/browser/views/frame/glass_browser_frame_view.cc?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/browser/views/frame/glass_browser_frame_view.h?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/browser/views/frame/opaque_browser_frame_view.cc?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/common/win_util.cc?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/common/win_util.h?r1=11416&r2=11415
   M http://src.chromium.org/viewvc/chrome/branches/169/src/chrome/views/window.cc?r1=11416&r2=11415

Merge r11355

Make Chromium windows not hide auto-hide taskbars, take 2.

This is very similar to r10845, but also includes a regression fix for  issue 8410 , where locking and unlocking the screen would cause mispositioning of child content.

Original Review URL: http://codereview.chromium.org/42027

BUG=20,8410
TBR= pkasting
Review URL: http://codereview.chromium.org/43066
------------------------------------------------------------------------

Typing this on the latest trunk build, so far so good.

Besides, the window is properly maximized after screen rotation as well. Hoorah!

Thanks!

Verified in build 2.0.170.0 (Developer Build 11440), works fine now.

I ventured to the Dev channel again with this fix included in the latest build. There 
is still a little unused space on the right when maximized, but much less than the 
latest Stable build.

Don't seem to notice unused space at the bottom, at least on this particular box.

Good job. : )

I've checked in winxpsp3 with the lastest from http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/ (is that correct?).
I have the startbar on the left, with autohide, without stayontop, and now I get 
'unused pixels' on the right, see attached.

	20090313chromiummax.PNG 6.1 KB   View   Download

Autohide + no always-on-top will result in a single row of unpainted pixels on each 
screen edge where an autohide bar exists.  This is about the best we can do right 
now.

I suggest using always-on-top, or not autohiding the taskbar :)

Ooops... Upon reading Peter's comments, I looked at the right edge again, and there 
isn't any unused space, but actually my always-on-top+auto-hide taskbar.

Cheers and have a nice weekend.

"I suggest using always-on-top"?! I suggest you learn about alt-tab. With the taskbar 
not always-on-top, it would be nice to have Chrome maximized use all of the screen, 
like any other application.

as per the comment 55, this works fine in 2.0.170.0 (Official Build 11755).

This is broken when using UltraMon to extend the taskbar to a second monitor. It works 
fine with UltraMon on the primary monitor but not on the secondary monitor. I.E. If 
Chrome is running on the first monitor everything works fine but if Chrome is running 
on the second monitor then the extended taskbar won't show under any known conditions. 
This is not the taskbar from the primary monitor but the extended taskbar which is 
enabled by UltraMon.

I forgot to mention that I'm running build 2.0.172.2 from the Dev channel.

I've had a look at
http://src.chromium.org/viewvc/chrome?view=rev&revision=11416
and I notice, in win_util.cc, bool EdgeHasAutoHideTaskbar is checking 
IsWindow(taskbar).
Shouldn't it check GetWindowLong(taskbar,GWL_STYLE)&&WS_EX_TOPMOST also?

I don't know as I have no knowledge of win32 programming

Filed that as  issue 9976 .

Please don't comment more on this bug.  File followup bugs as needed.  The original 
issue here is closed.

I'm noticing this bug again on Windows 7 on 2.0.177.1
Anyone else?

Me too, on Vista Home Premium 2.0.177.1 but not always, and when it happens I go to 
fullscreen and back again, and than it works ok for some time.

Nope, still works for me in 32bit WinXP.

Ya, it started working again for me.

Musta been a Windows 7 bug...

Just to kind of summarize for the less techie in the group what is going on here:

Vista\7 are treating Chrome as if it is a Full Screen Application. They are doing
this, because Chrome does not use a standard window, because of the way it is, we'll
say "Skinned." The way around this, is chrome can never take up 100% of your screen
even when it is maximized, we have to somehow get the window to redraw based on 1-2px
short of your max HeightxWidth. It is one of the drawbacks of not using the built in
window management\title bar that Firefox\Safari use on Win Vista\7. You can verify
this because Windows Messenger will set your status to "Busy" whenever Chrome is
maximized, which indicates that you are running a full screen application; Similar to
when you watch a flash video in full screen. What needs to be done is someone needs
to sit down and really weigh with the Mac and Linux versions how the skinning should
be applied, and whether it is worth re-working Chrome to support Native Windows Look
and Feel, to offset these problems; or if we really want to live with a 1-2px hole in
one side of the application so that we pay our price for having our Taskbar Hide.
Just some food for thought; I hope this helped you to understand why this is a very
important issue.

I would like to add that I for one, do not dislike how Safari 4 got around this; and
think that it supports tabs at the top in the best possible way; while maintaining
the look and feel of the platform.

same problem here. this bug and other issues made me hate google chrome and i don't 
like that. please fix it!

ra4king, what's the problem?

plugins don't work, google desktop also doesn't want to show up, most online games
don't work with Chrome are all problems i had and made me switch to Firefox. If
Google Chrome could be as prominent as firefox and internet explorer are, i would use
it forever but sadly no.

in reply to comments 108 and 149: would it be an idea to set the window size to more 
than the monitor resolution? I would have a go to set up a proof of concept but I'm 
not able to for the moment. If this is able to trick windows to now have the 
maximized-app-side-effects, it might be an issue on multiple monitor systems, but 
perhaps that's easier to treat. (e.g. SetWindowRegion?)

So has this issue been fixed or not - i'm having this problem sometimes. 

149 makes a valid point, I can confirm vista does treat chrome as a full screen 
application. But that doesn't change the fact that it needs to be fixed. Its really 
annoying, scrolling down to the bottom just to see that nothing happens. It really does 
need to be addressed.

This issue just started up again for me a few days back. Seems to have happened on both 
my XP box and Vista box at the same time.

For a second I thought it was fixed, I could access my beloved hidden task bar, but it 
turned out that it was just a one off. Back to "full screen" mode...

i sadly cannot use Google Chrome even if this problem has been fixed. Not many of the
plugins i use work with Google Chrome or even have a Google Chrome version.
Oh Google, I will still love your Gmail, Picasa, and Google Docs (even though I
prefer Microsoft Office Live Workspace, SORRY!!!).

I just install new 2.0.172.28 and this very anoying problem has reapeared.
I had no problem with 1.** version of chrome (but i remember having it with some 0.** 
version)

Confirm the issue's sporadic appearances on 2.0.172.30.

It was fine with 2.0.173.something.

Happens frequently on 2.0.181.1.  Not a deal breaker, but definitely a PITA.

Guys, I confirm that Google Chrome works perfectly in Windows 7. The taksbar always 
shows in full screen mode. It must be a problem with Vista then.

Windows 7 build 7127 x64, Chrome 2.0.181.1, the issue appears randomly, i can't 
reproduce the situation it does, but it does appear.

One last post to everyone commenting on this.

Sadly, Windows has numerous bugs relating to this issue, and problems like "sometimes 
it works but other times it hides taskbars until I minimize and restore" are examples 
of running into problems with Windows.  There isn't anything we can do about this.

The main problem here (that caused this to happen every single time on every machine) 
has been fixed as of the most recent versions of Chrome.  If you are not using 
version 2.0.172.28 or higher, please force an immediate update check via Tools->About 
Google Chrome.

No further work is planned because there are no problems known that are fixable on 
the Chrome side.

And now, removing email addresses so I can stop getting spammed about this.

I'm not sure what's the exact cause, but after updating a bunches of software last 
week, including a "downgrade" of Chrome from 2.0.173.x to 2.0.172.30. The problem re-
appeared.

Maybe the dev build is doing better, but I'm not ready to try that at this moment.

Cheers.

Using Windows vista and google chrome 2.0.181.1 in every channel i cannot use the 
windows taskbar. i have to minimize chrome in order to use it.
please, try to fix this, since it´s really annoying!
cheers from Argentina.

I'm a bit disapointed :/
This bug has been fixed in previous release (1.**) with a workaround (maximized
windows is a bit smaller than full screen).
Why they don't fix it again in 2.* like they did before? It's really anoying :(.

Strange behaviour than  saying "it's windows fault, bye"...

It's a Windows problem, not Chrome?  Give me a break.  If that were true, then why is 
Chrome the only browser or app that I use that has this problem?  Using Windows 7 RC, 
btw.

I'm going to guess, and say that the Windows issue comes with doing things the way 
Chrome does them.  That's why few other apps have this issue.

That's correct. Chrome is unique as it has no chrome. That's why it's called chrome.
Quote from wikipedia ( http://en.wikipedia.org/wiki/Chromium_(software) ):

"The name is derived from the graphical user interface frame, or "chrome", of web 
browsers."

Seems to occur when I do the following:

Launch Chrome
Minimize, then maximize
Wait for the taskbar to auto-hide

After that, taskbar won't show.

#172 suhayb.mohammed, that's exactly what I've noticed happening on XP Pro SP3.

#172-173 Same under win7. One thing that solves the problem is to enter and exit full 
screen mode (press F11 twice). After that, the problem does not occur again. (not even 
after minimizing-maximizing)

this issue has no CC or owner entry
so i suggest opening a new issue about it and link to it here

this is weird, you guys say that it appears in Windows 7 RC but I have not had any
problem with Google Chrome.

This just started popping up on dev vers 3.0.182.3
Annoying enough to have to switch my default browser back to firefox.  

Sorry, forgot to include OS in comment 177, Using Windows 7 RC1.  Sorry bout that.

jimbgreen, im also using Google Chrome version 3.0.182.3 on Developer channel and using 
Windows 7 RC and I'm having no problem. I have never had a problem with Google Chrome 
on any channel and all versions on Windows 7 RC.

Confirmed on my machine running Windows Vista Business and Chrome v. 2.0.172.28

Confirmed with Chromium 3.0.184.0 (17577)

Chrome 2 did'nt hinder the autohide function of Levono X61 with Vista.  Chrome 3 the 
problem appears.  Any solutions.

Had to disable autohide... this bug is annoying and nobody can seem to fix it.  Seems 
simple, but I guess not.  Back to using Firefox as my main browser, but would love to 
get back to Chrome as my primary once again.

Bug is still around even on the Beta version.  Taskbar seems to go behind/under Chrome 
browser. :(

The Full-Screen(F11) work-around seems to be the best way to temporarily fix the issue,  
and pressing F11 twice is not too much of a chore.

guys it works well windows 7. i have not experienced a problem yet with my taskbar.

Pressing th F11 twice will do for now... just annoying when it was working perfectly 
for months, then out of the blue it doesn't.  Hopefully an update will be in place and 
have a real fix on this bug.

Since the developers apparently don't give a damn about this issue, I devised a 
workaround using a free app called Autohotkey.  Using said app, I created a script that 
launches Chrome, then automatically presses F11 twice.  If anyone is interested in 
this, let me know and I'll post the script and details on how to configure it.

Hey, watch your mouth! It's an open source project, so we are all the developers!
That said, I friendly urge you to have a look at "view/window/window_win.cc"
At line 378 (in WindowWin::SetFullscreen) there's a SetWindowPos call that may be the 
real cause that your workaround works.

Also I must agree with the commenter there ("Better-looking methods welcome."), I've 
had better results using SetWindowPlacement instead of SetWindowPos.

stijnsanders, where can i find line 378?

here:
http://www.google.com/codesearch/p?hl=en&sa=N&cd=8&ct=rc#h0RrPvyPu-
c/views/window/window_win.cc&q=setfullscreen%20package:%22src.chromium.org/svn/trunk%22

or here:
http://src.chromium.org/viewvc/chrome/trunk/src/views/window/window_win.cc?view=markup

Confirmed bug on Chrome 2.0.172.31, running on Vista 32-bit home basic Svc Pak 1

Same problem here. Works fine with other browsers Firefox and IE. Some times taskbar 
get focus from chrome as well. If chrome is restored click out side on the task bar 
than maximize chrome now taskbar takes focus from chrome.

Same prob here, very irritating.

Bug confirmed on HP Pavillion dv6500 running both Vista Home Premium SP1 & Win7 RC, and 
HP Mini 1000 running WinXP Home SP3 & Win7 RC.  Very annoying problem, but F11 trick 
seems to work in the meantime.  Hope it get's fixed soon.  It's the only real problem I 
have with Chrome, and the only problem that occasionally makes me consider not using 
it.

Confirmed with Windows 7 RC

Confirmed with Windows 7 RC as well

People, can we stop confirming this bug?? We already know it is occurring on every 
version of Windows.  We don't need 90 emails sent out to tell us that again.

...and the Chromium team don't give a shit anyway, since they said it's not their 
problem and unsubscribed months ago. But hey, it's nice to be a part of an exotic 
subculture like this one.

I'm not sure whether it's a matter of "not giving a ****", or a matter of simply being 
unable to solve, and they don't need to be bothered with hearing people say "confirmed 
on this OS".

I think it's both actually, but what they did was basically giving us a finger and 
going their own way. Not very nice, especially since Chrome is like the only 
application in the Universe that has that problem [*]. And new confirmations only show 
that even on new systems the browser behaves badly.

[*] Ok, not really, but there's exception to every rule.

I guess what this "exotic sub-culture" needs is someone that digs into the source-code 
and has a close look at any code that is involved in this issue. I had a go over at 
comment 142, but I know only enough C to read and understand. I'm a novice at getting 
the source to build and getting into something like a debugger-ide to get the fingers 
dirty. (I've been doing Delphi most of my programmer-lifetime).

I confirm it too. Using Chromium 3.x and the problem still happens on Windows 7. 
Hitting F11 twice solves it, but its rather annoying. Someone please patch this, 
thanks!

Same problem in Windows 7 RC1 with Chrome 3.0.195.1 on a Dell Inspiron E1505.
The problem is intermittent in Windows 7 RC on a custom Core 2 Quad build. The task bar 
auto hides normally at first, but after a few minutes of use the problem occurs.

This is really the only problem that I have with Chrome. It's the only reason that I 
haven't switched 100% to Chrome yet. I'm surprised and disappointed that Google is so 
slow in fixing this problem. Google, please get this problem fixed!

Confirming issue in Windows 7 RC1 running Chrome 2.0.172.39 on an Inspiron 1720. 
Presents consistently.

Started using Chrome a little bit more but have to stop using as it is really bugging 
me this has not been fixed.  I downloaded chrome the day it came out and the problem 
was there then.  some sensible reason its not been fixed or is just to annoy windows 
users?

Probably the cost of hunting this down is too high and not many people use autohide 
anyway (IMO). I don't know how it looks like in beta/dev channels, but in stable you 
can live with this bug, especially since the workaround (2xF11) works.

Confirmed. Bug exists in Windows 7, too.

Is it okay to suggest that Chrome is an awful browser?  I would say 3/4 of the time
tabs don't load.  Why?  What am I doing wrong?  I need the autohide taskbar thing
fixed so I can easily start another browser when I get sick of Chrome.

I found another way to easily reproduce the problem. It seems to happen when the 
window gets restored to maximized from minimized without being the active window.

Having your taskbar already on auto-hide, simply press "Win-M" (Minimize All), then 
"Win-Shift-M" (Restore all). Chrome is now over the taskbar.

I also use a program called Switcher (http://insentient.net/) which uses Aero to 
implement a simili Exposé (from OS X). When I bring up Chrome from its minimized 
state using Switcher, it also triggers the bug.

On my 1280x800 screen, maximized Chrome has a window rect of (-8, -8)-(1288,808), 
whether the bug occurs or not. A "not over the taskbar" window will have a client 
rect of (8, 0)-(1288,806). When the bug occurs, the client rect is bumped to (8, 0)-
(1288,808). (2 more pixels vertically).

HTH,

JP

I reported the same problem... I had this program called Object Dock by Stardock which 
pops up whenever I mouse over it's location. (In this case I placed it on the top 
part).  For some reason it would interfere with Chrome.  I just placed the Object Dock 
to the bottom of the screen, and now it works perfectly like before.

The odd thing is, I have had this program before with Chrome and never ran into 
problems.  

Should this be marked windows specific?

I have this issue in Linux (KDE 4.3.0) too.

KDE 4.2.4 on Mandriva works fine for me.

confirm this issue on Chrome 4.0.206.1 Windows 7

I'm sorry if this is the wrong place, but I am finding another problem being caused by 
the same thing in Chrome. I gave up on Autohiding my taskbar, but when I've got Chrome 
open and the active window my screen never turns off, even though my power settings say 
to turn off the monitor after 5 minutes. If another application is in the foreground 
then the screen turns off fine. I assume that Windows is detecting Chrome as a full 
screen application and preventing the screen from turning off (like when watching a 
video). This is a really big problem...

I have the same issue. Had it under Vista with Chrome 2.x and now have it Win7 with 
Chrome 3.x. With Win7 the behaviour is more erratic. But after a while Chrome "takes 
over" even blocking out other windows like MSN.

I'm having a similar issue running Chrome 4.0.222.12 on Win 7 RTM.

vista SP2 64 + chrome 3.0.195.27 issue confirmed

Same issue in Windows 7 Professional, Chrome 3.0.195.27.

The F11 twice trick works, but would prefer not resorting to that.

This issue was incorrectly closed in March, as the issue is still not fixed. The 
problem is not Windows. Otherwise, millions of other applications would exhibit the 
same problem. A year later, and it is not fixed in any version of Chrome.

Please verify bugs are actually fixed before marking them as such.

Suggested fix for the users, since the developers are explicitly ignoring this issue 
(Comment #165, "And now, removing email addresses so I can stop getting spammed about 
this"): Uninstall Chrome and use any number of the other well developed browsers 
whose developers actually listen to bug reports.

Please fix this, I'm about to stop using Chrome as a result PURELY arising from this 
issue.

Confirmed issue in Windows 7 Ultimate, Chrome 4.0.245.0. This is absolutely annoying.

This can be worked around by setting the Start bar to Always On Top *after* you start 
Chrome. It's annoying, but it works.

im having the same problem on a windows 7 netbook.  i need all the screen space i can 
get and this is really annoying.  

I have just searched on the issue and came here - it seems to have been going on an 
awful long time... ?

See comment #165 and #220.

I'm still seeing the same problem. Maybe we should file a separate bug since the devs 
have all bug gone on this one...?

Confirmed, issue still exists with Windows 7 and latest Chrome build (3.0.195.33).  :(

Confirmed on MSI Wind U100 running Windows 7 Ultimate.

For those still seeing this issue, you may like to check out issue 9899, issue 12106, 
 issue 28042 , and star it/them as needed.

I think I may have found a solution. Try installing a theme from 
https://tools.google.com/chrome/intl/en/themes/index.html

I found out that themes stop the taskbar from hiding. When I uninstalled the theme. The 
taskbar hid after minimizing and maximizing the window. When I install it, I never see 
the problem.

Thanks ra4king, I just applied a theme (grayscale) and I have done about 1.5 hours of 
browsing without Chrome jumping ontop of my taskbar. I have been running multiple 
windows with multiple tabs and have minimized and swapped tasks through out the session 
and it is working perfect. BTW, I am running Chromium 35703 on Win7 x86 with Aero 
enabled.

Still an issue on Windows 7 as of 3.0.195.38. Sigh.

Still an issue on Windows 7, both in regular and beta channel chrome builds.

This is actually only an issue in Windows 7 if you place the taskbar on the left of the 
screen, with auto-hide enabled. (This is my preferred position on a netbook.)

nope, its the issue ALL over the place, I wonder why google can't fix a SIMPLE issue 
like this one? :-|

Please fix this, Google!

This continues in Windows 7 and dramatically affects Chrome usability on my netbook.

Please fix this

to solve the autohide issue, you just need to install a theme on your chrome. That'll 
fix it!

Tried installing a thme on chrome.  Issue did not resolve itself...still having 
problems.

BUG FOR AGES.
i have switched back the latest pre-alpha release of Opera because of this annoyance 
and you know what? Same bug there! I think it could be about the tabs-on-titlebar UI 
which Opera 10.50 adopted from Chrome.

Tried latest dev channel version (5.0.317.2 dev).  Still has the issue.

Tested it with and without themes.  No change.

Windows 7 Ultimate 64-bit.  Same issue but I didn't notice it until using a laptop 
where you have to autohide the taskbar to achieve somewhat adequate screen space.  I 
can't beleive that Google hasn't fixed this in the over 500 days that have passed since 
beta.

try a theme without transparency in the title bar it solve it for me. (like Mac OS 
theme it is the one I use).Effectively opera 10.5 beta have now the same issue

yup, this is still a problem, and quite annoying.

opera fixed this:
http://my.opera.com/desktopteam/blog/2010/02/19/post-beta-fixes

Alexander Kosenkov said in a discussion i saw....

I think, I know the root cause. 
Windows Taskbar (explorer.exe) has 'presentation mode'. For example, 
if you run Full-screen PowePoint presentation, Taskbar will be hidden. 
As far as I understand, Taskbar switches to that mode if some window 
has width & height of the screen and topleft position. 
Possible soulutions (needs code changes): 
1) Eaisest. Change windows size to 1 pixel less than the screen. This 
will prevent Taskbar from going idle. 
2) Right soultion. Find out how to tell Windows that our window is not 
'fullscreen' but it is just maximized (pobably some Window attribute 
should be set) 

http://stackoverflow.com/questions/137005/auto-hide-taskbar-not-appearing-when-my-
application-is-maximized

My problem is that Winamp will disappear.

To replicate:
 1. Open Winamp and set in Always on Top mode,
 2. Maximize Chromium,

Winamp will disappear behind Chromium.  Only happens when Chromium is maximized.

This is even worse with a Tablet PC, please fix this Google.

I use Windows 7. Same problem I can't get my taskbar appear when I max Google Chrome 

Same here, 32 bit Vista ultimate, taskbar on top, won't show if autohide is enabled. 
When will they repair it, anyway? It can't be really hard

Confirmed on HP Vista 64bit ultimate edition.

Confirm in window 7

Confirm in window 7

Same problem Windows 7 x64, it's really annoying :(

wtf google, fix this already! win7 home premium x64, chrome 4.0.249.89 (38071)

Same problem, still!! Why on earth hasn't this prevalent problem been fixed?

Another confirm with Win7 Pro x64.  D/Led Chrome 1hr ago.

Same problem, win7 pro x64, chrome 5.0.360.0 dev, this problem is really really 
annoying. Please, try to fix it in close future... thanks

Confirmed with Win7 Home Premium x64.  Chrome 4.1.249.1042 (42199).  I echo what a 
previous user says; this is super-frustrating with a tablet, when there's not even a 
Windows key to fall back on.

Confirmed w/ a toshiba satellite on Windows 7 Pro

Nearly 1.5 years on and still no solution to the problem. Come on Google. 

I can't believe this problem still exists. Running a theme seamed to help but even that 
doesn't seam to help anymore. For those on netbook without a windows key, you can hit 
Ctrl+Esc to bring up the start menu.

Seriously...1 and a half years.  Love chrome but this is really annoying!

Confirmed on Lenovo, Win7 Ultimate 32-bit. This issue drives me nuts and even though 
developers know that this is a legit concern (look at the number of comments here, for 
example), they've not done anything to address it yet.

F11, F11 works well.. I just wish I didn't have to do this 300 times a day. :)

just installed chrome on 7 Home Premium and its doing the same thing for me, have to 
either minimize chrome or hit the start button to get to the auto hid taskbar.  such a 
pain in the butt.  but chrome is still running better than firefox did so i'm not 
fussing to bad.

Yep yep, still going on. This is why I stopped using chrome a while ago. Hitting F11 
twice is a temporary fix, but I really can't believe google knew about this bug all 
this time and *still* cannot fix things. This does not happen with any of my other 
browsers (all the latest versions, of course).

I'm very, very disappointed, especially considering the support team marked the issue 
"closed" a year ago when it obviously was not.

Just putting my vote in for PLEASE FIX...

Just got a Netbook, and and Chrome is awesome for it... Auto-hide Win7 Taskbar is a 
must.

guys the desktop coral thing works great and takes 5 minutes....just go for that

I am having similar problems. I really love the Chrome browser but I am accustomed to 
auto-hide taskbar. Have been since Windows 95. I am currently using Vista. As reluctant 
I am but this just might make me go back to Firefox. Please Google, fix this..quick!

Confirming this issue. Vista Business 32bit Chrome 5.0.375.7 dev

I didn't start noticing this issue until I installed a couple of plug-ins. I thought 
that might have something to do with it until I came across this thread.

Are there any plans to get this fixed soon?

also having this problem...kind of annoying =)

Comment #165, are you serious? Fixed as of version 2.something? I have version 
4.1.249.1045 (42898) and it still constantly affects me. I would love to stay with 
GC, but this is far too annoying. Maybe someday, when you grow up, you will be a real 
developer, and you will take your product and it's users seriously. Until then, I'm 
going back to FF. Sure, it may be more bloated and take twice as long to start up, 
but at least the guys who develop FF don't think their browser is better and more 
functional than the OS it's running on.

Every other program plays nice with the Taskbar Autohide feature. Why can't you 
comply with the MS standard? Even independent freeware developers seem to have no 
trouble with this. It seems as though you think your programming is superior to that 
of Microsoft, when clearly, it isn't. "Rough around the edges" would be a great 
complement to your skills as a programmer, and even then, that's giving far more 
credit than is due. Google HR needs to seriously reconsider their decision to employ 
you, because you certainly aren't ready to roll with the big boys.

This post is being written using Google Chrome, which is the last thing that I'm 
going to do with it, other than uninstall it.

I have been running 5.0.384.0 (45177) all day and so far so good.

http://build.chromium.org/buildbot/continuous/LATEST/mini_installer.exe

Anyone else think this issue is related to switching to presentation mode? I noticed I 
only started having this problem after I gave a powerpoint presentation for class.

Well I think it is safe to say this problem is fixed. For me anyways. I was having to 
F11 F11 constantly up until build 45177. I have not had it mess up a single time since.

I switched from Chromium back to Chrome Dev (5.0.375.17 (Official Build 45275) dev) and 
the autohide problem is back. This is such a pain. There is this bug preventing me from 
using Chrome and another bug preventing me from using Chromium. I wish they would merge 
the autohide fix into the main build.

We fixed another issue relating to autohide taskbars in r44941.  This is currently only 
available in trunk builds, not in the Dev channel releases.  I will make sure this fix 
gets merged to Chrome 5.  In the meantime, if you try a trunk (not Dev) build after 
44941, please note whether your problems have been fixed or still persist.

Update: This has now been merged onto the Chrome 5 branch.  It will not be in the next 
beta channel release, but it will be in the final version of Chrome 5.

Has this been dropped out of the Chrome dev channels?  It's not working for me (Win 7) 
on Chrome dev 6.0.401.1?  Or is comment 278 still applicable?

Google Chrome is the only application I have that is causing this problem.  It is 
annoying enough for me to go back to using Firefox.

Sadly this long standing issue and the way developers dealt with it show the kind of 
respect that users should expect from the team. Such a shame about the great work 
guys working at V8 and other places of the browser if such an obvious and hurting bug 
in the eyes of the users remain ignored (it's about the main window of the 
application screwing with the OS, not an obscure feature). This wouldn't happen in a 
commercial company where respect for users do count.
Opera 10.5 deals perfectly within the very same circumstance so it can be fixed.
I am sure that Microsoft guys if asked will gladly provide the fix (anyone remembers 
how they worked with Firefox team to help fix FF for Win7?). It's about asking and 
getting a quick answer.
It's just about that: do your users worth more than your ego?

I am also experiencing this problem in the new beta version of firefox 4 which is funny because there is no top bar for its interface also like chrome's and how the tabs are on top.

i have not used chrome for close to 2 years because of this annoying issue.

FIX IT and I will be the first to re-download chrome...

and yes, it still doesn't work