Closed Bug 597353 Opened 14 years ago Closed 14 years ago

Ensure pinned tabs have the same height and alignment as normal tabs

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 4.0b7
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: dao, Assigned: dao)

References

Details

Attachments

(1 file, 2 obsolete files)

vertical-align:middle is different from centered alignment in XUL, as the former depends on the font metrics which can have unequal padding at the top and the bottom. Enabling DirectWrite shows this problem or even just increasing the font size regardless of DirectWrite. vertical-align:middle on the tab stack is also wrong for the progress line which isn't supposed to be centered. So instead we need to make sure that the tab-content container has the same height for app tabs and normal tabs. Squeezing the label instead of completely removing it achieves this.
Attached patch patch (obsolete) (deleted) — Splinter Review
Attachment #476204 - Flags: review?(gavin.sharp)
Blocks: 585164, 544820
blocking2.0: --- → ?
Blocks: 597307
Comment on attachment 476204 [details] [diff] [review] patch Changing the vertical align seems to actually make the favicon alignment worse... http://grab.by/6r3i http://grab.by/6r3x
(In reply to comment #2) > Comment on attachment 476204 [details] [diff] [review] > patch > > Changing the vertical align seems to actually make the favicon alignment > worse... > http://grab.by/6r3i > http://grab.by/6r3x 6r3i is with the patch and 6r3x without it? tab-content has align="center", so this should take care of the alignment as long as the box height for app tabs is the same as for normal tabs. This worked for me on Windows and Linux, but maybe there's something Mac-specific that I'm missing.
Both screenshots have the .tab-label[pinned] hunk applied. 6r3i includes the change to "vertical-align: top" for .tab-stack, 6r3x does not.
Attached patch patch v2 (obsolete) (deleted) — Splinter Review
this should fix pinstripe
Attachment #476204 - Attachment is obsolete: true
Attachment #476496 - Flags: review?(gavin.sharp)
Attachment #476204 - Flags: review?(gavin.sharp)
blocking2.0: ? → final+
This needs to be fixed sooner than right before RC, ideally for beta 8. This is a central piece of CSS, I don't want to see more theme changes building on the misalignment. Also, this will affect third-party themes. Also, if for some reason this doesn't always work as expected, we'd want to find out about it as soon as possible.
blocking2.0: final+ → ?
Good points. I final+'d it as polish, but you're right that themers could compound the problem here if they treat it as given. I agree that beta8 would be ideal, but I wouldn't hold a specific beta for it, so bumping to betaN
blocking2.0: ? → betaN+
(In reply to comment #6) > This is a central piece of CSS, I don't want to see more theme changes building > on the misalignment. Happening in bug 597592 right now :/
Blocks: 597592
Comment on attachment 476496 [details] [diff] [review] patch v2 Can you add a comment explaining where the 19px comes from?
Attachment #476496 - Flags: review?(gavin.sharp) → review+
Attached patch patch v2 (comment added) (deleted) — Splinter Review
I'd like to land this for beta7 in preparation for bug 597592, which is wanted for that beta.
Attachment #476496 - Attachment is obsolete: true
Attachment #479366 - Flags: approval2.0?
Comment on attachment 479366 [details] [diff] [review] patch v2 (comment added) bug 597592 now blocks beta 7.
Attachment #479366 - Flags: approval2.0?
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b7
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: