Closed
Bug 470711
Opened 16 years ago
Closed 16 years ago
Newly modernized tabs look cut off if the last one is hidden
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
VERIFIED
FIXED
mozilla1.9.1b3
People
(Reporter: mozilla.org, Assigned: mstange)
References
Details
(Keywords: regression, verified1.9.1)
Attachments
(3 files, 1 obsolete file)
9.36 KB,
image/png
|
Details | |
1.81 KB,
patch
|
roc
:
review+
jaas
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
1.91 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
The folder properties dialog for local folders is drawn improperly; the rounded corners on the Retention Policy tab do not show. See the screen shot. To duplicate: right click on Local Folders -> Inbox and select Properties. Using 3.0b1 on Mac OS X Intel. Sorry if this is a dupe; I searched but did not find anything similar.
Flags: wanted-thunderbird3?
Flags: blocking-thunderbird3?
Comment 1•16 years ago
|
||
Markus: thoughts? It's http://mxr.mozilla.org/comm-central/source/mailnews/base/resources/content/folderProps.xul#66 where http://mxr.mozilla.org/comm-central/source/mailnews/base/resources/content/folderProps.js#273 sets .hidden on things including the last tab onload.
Blocks: 231313
Version: unspecified → Trunk
Comment 2•16 years ago
|
||
Though even if we work around it in that dialog, there's still who knows how many extensions doing it (Enigmail was the one I saw a screenshot of this morning), and I don't think we want the solution to be an MDC paragraph saying "even though it looks like it works just fine to set a <tab> to .hidden, don't do it, because it looks like crap on OS X."
Assignee: nobody → joshmoz
Severity: trivial → normal
Component: Mail Window Front End → Widget: Cocoa
Flags: wanted-thunderbird3?
Flags: blocking-thunderbird3?
Keywords: regression
Product: Thunderbird → Core
QA Contact: front-end → cocoa
Summary: improperly drawn tabs in folder properties dialog for local folders → Newly modernized tabs look cut off if the last one is hidden
Updated•16 years ago
|
Flags: blocking1.9.1?
Assignee | ||
Comment 3•16 years ago
|
||
The appearance of the tabs is based on the presence of the "first-tab" / "last-tab" attributes. So we should probably update them whenever .hidden changes.
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•16 years ago
|
||
This patch implements what I outlined in the previous comment.
Attachment #354569 -
Flags: review?(neil)
Comment 5•16 years ago
|
||
Comment on attachment 354569 [details] [diff] [review] tabbox.xml approach, v1 >+ this.setAttribute("hidden", val ? "true" : "false"); Setting .hidden = false should remove the attribute.
Comment 6•16 years ago
|
||
Also, this won't work for .setAttribute("hidden", "true") or using display:none directly. This could probably be fixed by calling updateVisibilityFlags from the tab constructor and destructor. Or is there away to fix this on the widget level so that the first/last-tab attributes aren't needed at all?
Assignee | ||
Comment 7•16 years ago
|
||
> Or is there away to fix this on the widget
> level so that the first/last-tab attributes aren't needed at all?
Yeah, and that's even easier. The only disadvantage of this approach is that theme developers who style the tabs with CSS don't benefit from it.
Attachment #354569 -
Attachment is obsolete: true
Attachment #354608 -
Flags: review?(roc)
Attachment #354569 -
Flags: review?(neil)
Attachment #354608 -
Flags: review?(roc) → review+
Attachment #354608 -
Flags: superreview?(roc)
Comment on attachment 354608 [details] [diff] [review] nsNativeTheme approach, v1 >+ nsIFrame* first = aFrame->GetParent()->GetFirstChild(NULL); Argument to GetFirstChild should be nsnull.
Attachment #354608 -
Flags: review+
Attachment #354608 -
Flags: superreview?(roc) → superreview+
Assignee | ||
Comment 9•16 years ago
|
||
pushed: http://hg.mozilla.org/mozilla-central/rev/823c957d952e
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
Assignee | ||
Comment 10•16 years ago
|
||
Landed on 1.9.1: http://hg.mozilla.org/releases/mozilla-1.9.1/rev/50b1f7631625
Keywords: fixed1.9.1
Comment 11•16 years ago
|
||
We don't have a possibility to test this automatically, right? Can we get a simple testcase which shows the broken behavior? It would be nice to have it in Litmus at least.
Flags: in-testsuite?
Flags: in-litmus?
Target Milestone: mozilla1.9.2a1 → mozilla1.9.1b3
Assignee | ||
Comment 12•16 years ago
|
||
It's possible to write a reftest for this. I'll make one.
Assignee | ||
Comment 13•16 years ago
|
||
Attachment #355221 -
Flags: review?(roc)
Comment 14•16 years ago
|
||
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090103 Shredder/3.0b2pre ID:20090103025757
Attachment #355221 -
Flags: review?(roc) → review+
Assignee | ||
Comment 15•16 years ago
|
||
Checked in the reftest on both mozilla-central and mozilla-1.9.1.
Assignee | ||
Updated•16 years ago
|
Flags: in-testsuite? → in-testsuite+
Comment 16•16 years ago
|
||
Just for information: http://hg.mozilla.org/mozilla-central/rev/e38385c26b20 http://hg.mozilla.org/releases/mozilla-1.9.1/rev/c605e0375e2e
You need to log in
before you can comment on or make changes to this bug.
Description
•