Closed
Bug 351965
Opened 19 years ago
Closed 19 years ago
Disable background close looks evil in the new themes
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2
People
(Reporter: philor, Assigned: philor)
References
Details
(Keywords: fixed1.8.1, polish, Whiteboard: [Fx2 theme change])
Attachments
(3 files, 3 obsolete files)
|
15.98 KB,
image/png
|
Details | |
|
10.13 KB,
patch
|
asaf
:
review+
|
Details | Diff | Splinter Review |
|
11.65 KB,
patch
|
mconnor
:
approval1.8.1+
|
Details | Diff | Splinter Review |
The visual refresh seems to have forgotten about browser.tabs.disableBackgroundClose - set it to true and your nonselected tabs have a strange and terrible and off-center strip of lowered opacity running clear through them. If nobody figures out a way to fix it so the buttons look disabled, rather than looking like someone took a swipe at them with a paintbrush, we should just go for no change in appearance, and if it's written to survive not having a default value, think about taking it out of firefox.js so people aren't tempted to see our brokenness.
| Assignee | ||
Comment 1•19 years ago
|
||
| Assignee | ||
Updated•19 years ago
|
Flags: blocking-firefox2?
Comment 2•19 years ago
|
||
I don't understand how browser.tabs.disableBackgroundClose=true is different from browser.tabs.closeButtons=0. It looks different, sure, but to what end? imho browser.tabs.disableBackgroundClose can/should be removed.
| Assignee | ||
Comment 3•19 years ago
|
||
I'd say the primary difference is that you're several thousand times more likely to inadvertently double-click a background tab in the area where the close button isn't yet, and accidentally close it, with closeButtons=0.
| Assignee | ||
Comment 4•19 years ago
|
||
(In reply to comment #3)
> inadvertently double-click a background tab
For which Mano filed bug 352021
| Assignee | ||
Comment 5•19 years ago
|
||
This should be a minimal removal - there's a little more related stuff in browser.css, but it's mingled with other stuff, and I'd rather take a new bug to strip it all out once the visual refresh lands on the trunk and the branch is gone. (Branch patch to come, because some unsynced whitespace at the end of a line on branch is confusing patch.)
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Attachment #237686 -
Flags: review?(bugs.mano)
| Assignee | ||
Comment 6•19 years ago
|
||
Comment 7•19 years ago
|
||
we typically don't block on bugs with hidden prefs, and never this late.
would likely take the patch though.
Flags: blocking-firefox2? → blocking-firefox2-
| Assignee | ||
Comment 8•19 years ago
|
||
Bah, last branch patch didn't actually remove the pref. I must have been too shocked by all that trailing whitespace.
Attachment #237687 -
Attachment is obsolete: true
Comment 9•19 years ago
|
||
*** Bug 350034 has been marked as a duplicate of this bug. ***
Comment 10•19 years ago
|
||
Comment on attachment 237686 [details] [diff] [review]
Remove it (trunk)
You should also remove tab-close-button-placeholder entirely (i.e. xul.css, tabbrowser-tab binding in tabbrowser.xml and in globablBindings.xml of each theme, browser.css files of each toolkit theme).
Thanks for exposing browser.tabs.closeButtons while you're here.
Attachment #237686 -
Flags: review?(bugs.mano) → review-
| Assignee | ||
Comment 11•19 years ago
|
||
Hmm, yeah. I don't know why removing something that's always display:none seemed like a scary change to me last night.
Attachment #237686 -
Attachment is obsolete: true
Attachment #237711 -
Attachment is obsolete: true
Attachment #237921 -
Flags: review?(bugs.mano)
Comment 12•19 years ago
|
||
Comment on attachment 237921 [details] [diff] [review]
Really remove it all (trunk)
r=mano. On branch, you also need to tweak the winstripe-specific binding.
Attachment #237921 -
Flags: review?(bugs.mano) → review+
| Assignee | ||
Updated•19 years ago
|
Whiteboard: [checkin needed]
| Assignee | ||
Comment 13•19 years ago
|
||
philor:~/moz18/mozilla$ grep -r "button-place" ./
philor:~/moz18/mozilla$
Attachment #237938 -
Flags: approval1.8.1?
Updated•19 years ago
|
Keywords: polish
Whiteboard: [checkin needed] → [Fx2 theme change][checkin needed]
Comment 14•19 years ago
|
||
mozilla/toolkit/themes/pinstripe/global/browser.css 1.15
mozilla/toolkit/content/widgets/tabbrowser.xml 1.200
mozilla/toolkit/content/xul.css 1.86
mozilla/toolkit/themes/winstripe/global/browser.css 1.19
mozilla/browser/app/profile/firefox.js 1.161
mozilla/toolkit/themes/pinstripe/global/globalBindings.xml 1.17
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [Fx2 theme change][checkin needed] → [needs approval][Fx2 theme change]
Comment 15•19 years ago
|
||
Comment on attachment 237938 [details] [diff] [review]
Really remove it all (branch)
a=mconnor on behalf of drivers, please get this in ASAP (tonight if possible)
Attachment #237938 -
Flags: approval1.8.1? → approval1.8.1+
Comment 16•19 years ago
|
||
1.8 branch:
mozilla/browser/app/profile/firefox.js 1.71.2.73
mozilla/toolkit/content/xul.css 1.61.2.20
mozilla/toolkit/content/widgets/tabbrowser.xml 1.103.2.92
mozilla/toolkit/themes/pinstripe/global/browser.css 1.7.4.19
mozilla/toolkit/themes/pinstripe/global/globalBindings.xml 1.3.12.13
mozilla/toolkit/themes/winstripe/global/browser.css 1.9.4.30
mozilla/toolkit/themes/winstripe/global/globalBindings.xml 1.3.24.4
Keywords: fixed1.8.1
Whiteboard: [needs approval][Fx2 theme change] → [Fx2 theme change]
| Assignee | ||
Updated•19 years ago
|
Whiteboard: [Fx2 theme change] → [Fx2 theme change][checkin needed (1.8 branch)]
| Assignee | ||
Updated•19 years ago
|
Whiteboard: [Fx2 theme change][checkin needed (1.8 branch)] → [Fx2 theme change]
You need to log in
before you can comment on or make changes to this bug.
Description
•