Open Bug 741404 Opened 13 years ago Updated 2 years ago

Give extension developers the ability to turn off glass caption buttons

Categories

(Core :: Widget: Win32, defect)

x86_64
Windows 7
defect

Tracking

()

People

(Reporter: jimm, Unassigned)

References

Details

(Whiteboard: tpi:-)

Spin off from bug 730219. Some extension developers would like the ability to turn off window caption buttons. On XP and aero basic with the fx button displayed this is easy to do. On non-fx button windows and aero glass windows it is not. We have the ability to control the visible of these controls through widget but we currently don't expose it to chrome content.
Just launched latest nightly 15.0a1, issue is still not resolved. Do we have any progress here?
Ability to remove/hide or somehow disable the titlebar with its buttons would be much appreciated. Every vertical pixel gained would enhance web content viewing. Specially in windowed mode (maximized or not), as full screen viewing is not always the most suitable mode to work with using multiple applications. I already use tree style tab, and disable the navigation toolbar on occasions. The last frontier is most certainly the omnipresent eyesore that is the titlebar. However, I do need to point out that moving the window in some other manner would need to be reimplemented (e.g.: by using alt+mouse move or any combinations or #addon-bar background or even tree style tab background). Regards from Canada, Paul
This would be 100% possible to do without a doubt at all. If you install this user style with stylish: http://userstyles.org/styles/41182/firefox-7-about-blank-glass on Firefox, it removes the background from fullscreen, and it reveals that they do, in fact, have aero without the default caption buttons underneath the fullscreen's (which looks like a re-sized restored window with the style) background, and that they use the custom buttons in place of them. So that PROVES that this is 100% WITHOUT A DOUBT possible.
Depends on: 975822
Whiteboard: tpi:-
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.