183609 - NS_THEME_TAB tab widget doesn't join horizontal bar correctly

Status: RESOLVED INVALID

(SeaMonkey :: Themes, defect)

Description

[Greg K.]

Mozilla's NS_THEME_TAB implementation on Mac doesn't result in tab widgets that
are correctly joined to the blue horizontal bar. (Tested using the Classic theme
and FizzillaMach/2002112607.)

Comment 1

[Greg K.]

Attachment: Example XUL file containg a tabbox structure

Comment 2

[Greg K.]

Attachment: Screen capture of FizzillaMach/2002112607 displaying the testcase using the Classic theme

Comment 3

[Greg K.]

Attachment: Screen capture of Apple's Network Utility application showing authentic Aqua tab box structure

Comment 4

[Greg K.]

Note that Gerich figured out how to fix this in his Pinstripe theme.

Comment 5

[Greg K.]

*** This bug has been marked as a duplicate of 192029 ***

Comment 6

[Greg K.]

Bug 192029 fixed the tabbrowser bar, but not those in normal XUL tabboxes.
Reopening.

Comment 7

[Greg K.]

Reassigning to Themes as bug 192029 was assigned.

Comment 8

[Greg K.]

From Gerich: "...in order for the tab panel to be *under* the tabs so they can
overlap, the tabpanel would have to be have to come before the tabs in the XUL
code. This is how it looks now in XUL (pseudocode):

<tabbox>
    <tabs>
    <tabpanel>
</tabbox>

if I could change the XUL like this:

<tabbox>
    <tabpanel>
    <tabs>
</tabbox>

then I could use the trick that I used on the browser tabs to get them to
overlap slightly. I'm not sure how to do this with XBL but I'll give it another
look soon."

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Stefan [:stefanh]]

I'm resolving this as invalid since we're now using post-10.2 tabs and they don't have a horizontal bar.