Closed Bug 582819 Opened 14 years ago Closed 14 years ago

[win7] UI issue when Aero Border Padding set to 0 instead of 4 (default)

Categories

(Core :: Widget: Win32, defect)

x86
Windows 7
defect
Not set
trivial

Tracking

()

RESOLVED FIXED

People

(Reporter: cheesegoduk, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100728 Minefield/4.0b3pre
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100728 Minefield/4.0b3pre

Hi Folks,
I currently set my Windows Aero border padding to 0 (Right click desktop > Personalization > Window Color > Advanced Appearance Settings > Border Padding > 0) As I'm not a fan of having big borders around my Aero Windows.

However, when I do this and turn off the menu bar in builds of Firefox 4 I get the issue below :-
[img]http://a.imageshack.us/img718/752/minefieldq.jpg[/img]
(The space above the "Minefield" button)
It happens when I maximise a window and also prevents me from using the "Pull" away feature of windows 7 to move a maximised window if I click in any space above the button.
Whist I realise I've modified the default Windows 7 UI and the issue isn't the end of the world, given that for the moment I can just use the old menu bar, It would be nice if I could fix it somehow without turning borders back on...


Reproducible: Always

Steps to Reproduce:
1. Right click desktop > Personalization > Window Color > Advanced Appearance Settings > Border Padding > 0
2. Load Firefox/Minefield and turn off the old menu bar
3. Maximise the Window
4. Line will appear above the new "Firefox/Minefield" button that is unresponsive to the "pull" away feature of maximised windows included with Windows 7


Expected Results:  
Draw the UI regardless of border padding settings.

Default theme, no addons active.
D2D set on.
Severity: normal → trivial
Component: Theme → Widget: Win32
Product: Firefox → Core
QA Contact: theme → win32
I didn't even realize this was possible. CC'ing Jim. Not immediately clear to me how we can query this theme value and fix it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bug 576960 is similar. The new css style props should be populated with these defaults so positioning is correct.
Depends on: 575870
Dupe of Bug 581023?
Fixed by the landings in bug 575870 & bug 574454.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.