ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
Jasoco said:That's Maximized. Not fullscreen. Fullscreen is a bit different. What does it do on Windows when you use Chrome's Fullscreen option? Fake edit: Well now. Windows Chrome doesn't have a Fullscreen option? What gives? I guess Fullscreen must be an OS X thing.
Mac OS X Fullscreen® is different from what everyone has been calling fullscreen since forever. F11 initiates the "Windows version" of fullscreen, with the page taking up the whole view area, without any of the browser or OS chrome whatsoever.
Jasoco said:Which is interesting because Fullscreen makes the window take up the WHOLE screen including removing the menubar and Dock. Does Linux have Fullscreen?
I'm sure it does.
Jasoco said:Windows with Maximizing:
http://i.min.us/il00y4.PNG[IMG]
OS X with Fullscreen:
[IMG]http://i.min.us/il026C.PNG[IMG]
You get more pixels in OS X.[/quote]
Setting the taskbar to auto-hide or the slimmed down version would essentially be the same thing.
I find it odd this is some great new feature for OS X. Have Mac apps really been without a maximization option for this long?
[QUOTE=Jasoco]And would get even more if they removed the top buffer. Of course, this is Chrome Canary so hopefully someone realizes this before release. But I assume they kept the buffer there to prevent activating the menubar. Which is why it should have a delay. But I suspect the menubar slide delay is controlled by OS X and not the app developer.[/QUOTE]
I would imagine so. It's pointless to complain about Dev/Canary glitches or drawbacks, really.