Closed Bug 495214 Opened 15 years ago Closed 15 years ago

Refresh tab strip arrows on Windows

Categories

(Firefox :: Theme, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 3.6a1

People

(Reporter: faaborg, Assigned: ehsan.akhgari)

Details

(Keywords: fixed1.9.1, Whiteboard: [icon-shiretoko][icon-complete])

Attachments

(4 files, 10 obsolete files)

Theme bug for refreshed tab strip arrows on XP and Vista.
Whiteboard: [icon-shiretoko][icon-complete]
Attached image tab-arrow-end-aero.png (obsolete) —
Attached image tab-arrow-start-aero.png (obsolete) —
Attached image tab-arrow-end.png (obsolete) —
Attached image tab-arrow-start.png (obsolete) —
Image size had to be increased to 15x19 for each arrow to accommodate the glow on the hit state.  Order is:

normal / hover / disabled / hit

in all images.
The hit state in tab-arrow-end-aero.png is significantly darker than in tab-arrow-end.png, whereas tab-arrow-start.png and tab-arrow-start-aero.png are almost identical.
Attached image tab-arrow-end.png with less fail (obsolete) —
sorry, hit layer had opacity problem, fixed
Attachment #380093 - Attachment is obsolete: true
the -aero are both a darker blue, and the xp icons use a brighter blue, they should all match their counterparts now.
Assignee: nobody → ehsan.akhgari
Status: NEW → ASSIGNED
Attached patch Patch (v1) (obsolete) — Splinter Review
Attachment #380121 - Flags: review?(dao)
Attached patch Patch (v2) (obsolete) — Splinter Review
Compensate the height difference of the new images to make sure the tab strip doesn't get taller with this patch (the toolbar buttons' heights remain 23px).
Attachment #380121 - Attachment is obsolete: true
Attachment #380154 - Flags: review?(dao)
Attachment #380121 - Flags: review?(dao)
(this has my pre-approval to land on mozilla-central once reviewed, please nominate for a191 when that happens)
(In reply to comment #10)
> Created an attachment (id=380154) [details]
> Patch (v2)
> 
> Compensate the height difference of the new images to make sure the tab strip
> doesn't get taller with this patch (the toolbar buttons' heights remain 23px).

So that patch cuts off the top and bottom lines of the images.

Alex, can we get images with a height of 17px instead?
Comment on attachment 380154 [details] [diff] [review]
Patch (v2)

> .tabbrowser-arrowscrollbox > .scrollbutton-down > .toolbarbutton-icon {
>-  margin-top: 5px;
>-  margin-bottom: 1px;
>   -moz-margin-end: 2px;
> }

Looks like you need to remove the remaining margin too; makes the button overly wide.
Attachment #380154 - Flags: review?(dao)
(In reply to comment #12)
> (In reply to comment #10)
> > Created an attachment (id=380154) [details] [details]
> > Patch (v2)
> > 
> > Compensate the height difference of the new images to make sure the tab strip
> > doesn't get taller with this patch (the toolbar buttons' heights remain 23px).
> 
> So that patch cuts off the top and bottom lines of the images.
> 
> Alex, can we get images with a height of 17px instead?

Yes, FWIW the top and bottom lines were empty pixels.
Whiteboard: [icon-shiretoko][icon-complete] → [icon-shiretoko][icon-needed]
Attached patch Patch (v2.1) (obsolete) — Splinter Review
Addressed comment 13 for now...
Attachment #380154 - Attachment is obsolete: true
Attachment #380452 - Flags: review?(dao)
Comment on attachment 380452 [details] [diff] [review]
Patch (v2.1)

needs fixed image files
Attachment #380452 - Flags: review?(dao) → review-
Attached file Tab strip arrows, all 17 pixels tall (obsolete) —
Attachment #380091 - Attachment is obsolete: true
Attachment #380092 - Attachment is obsolete: true
Attachment #380094 - Attachment is obsolete: true
Attachment #380097 - Attachment is obsolete: true
Ehsan, while you're at it, care to rename the files from arrow-start and arrow-end to arrow-left and arrow-right?
Whiteboard: [icon-shiretoko][icon-needed] → [icon-shiretoko][icon-complete]
Attached patch Patch (v3)Splinter Review
Patch with new icons.

(In reply to comment #18)
> Ehsan, while you're at it, care to rename the files from arrow-start and
> arrow-end to arrow-left and arrow-right?

Done.
Attachment #380452 - Attachment is obsolete: true
Attachment #380605 - Flags: review?(dao)
Comment on attachment 380605 [details] [diff] [review]
Patch (v3)

>+.tabbrowser-arrowscrollbox > .scrollbutton-up:not([disabled="true"]),
>+.tabbrowser-arrowscrollbox > .scrollbutton-down:not([disabled="true"]) {
>+  -moz-image-region: rect(0, 15px, 17px, 0);
>+}

:not([disabled="true"]) is not needed here, AFAICT.

Otherwise looks good, code-wise. I haven't tested this again, I hope you have!
Attachment #380605 - Flags: review?(dao) → review+
Comment on attachment 380605 [details] [diff] [review]
Patch (v3)

>+        skin/classic/browser/tabbrowser/tab-arrow-right.png                     (tabbrowser/tab-arrow-right.png)
>+        skin/classic/browser/tabbrowser/tab-arrow-left.png                      (tabbrowser/tab-arrow-left.png)

nit: "left" precedes "right" alphabetically.
(In reply to comment #20)
> (From update of attachment 380605 [details] [diff] [review])
> >+.tabbrowser-arrowscrollbox > .scrollbutton-up:not([disabled="true"]),
> >+.tabbrowser-arrowscrollbox > .scrollbutton-down:not([disabled="true"]) {
> >+  -moz-image-region: rect(0, 15px, 17px, 0);
> >+}
> 
> :not([disabled="true"]) is not needed here, AFAICT.

Yes, I was just imitating the :hover rules below it.  Will fix upon landing.

> Otherwise looks good, code-wise. I haven't tested this again, I hope you have!

Yes, I have!  :-)

(In reply to comment #21)
> (From update of attachment 380605 [details] [diff] [review])
> >+        skin/classic/browser/tabbrowser/tab-arrow-right.png                     (tabbrowser/tab-arrow-right.png)
> >+        skin/classic/browser/tabbrowser/tab-arrow-left.png                      (tabbrowser/tab-arrow-left.png)
> 
> nit: "left" precedes "right" alphabetically.

Will fix upon landing.

BTW, I assume that we don't want to rename the existing images on branch, right?
http://hg.mozilla.org/mozilla-central/rev/543dfafa466a
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.6a1
hg did some crazy stuff because the binary image files were both changed and renamed, which caused the change not to take affect.  Pushed icons in a separate round: <http://hg.mozilla.org/mozilla-central/rev/625ef204187e>
Attached patch 1.9.1 Patch (obsolete) — Splinter Review
Branch patch without renaming the images.
Attachment #380609 - Flags: approval1.9.1?
(In reply to comment #22)
> BTW, I assume that we don't want to rename the existing images on branch,
> right?

If someone is using them, we're breaking that anyway, as the dimensions change.

I missed that you removed opacity:0.4 from the disabled state. Why have you done that?
Attachment #380609 - Flags: approval1.9.1?
(In reply to comment #26)
> (In reply to comment #22)
> > BTW, I assume that we don't want to rename the existing images on branch,
> > right?
> 
> If someone is using them, we're breaking that anyway, as the dimensions change.

OK, I'll provide a new 1.9.1 patch then.

> I missed that you removed opacity:0.4 from the disabled state. Why have you
> done that?

Because previously we turned down the opacity in disabled mode using the normal image.  Now, we're using a dedicated disabled state, so I assumed that it's no longer needed.  Am I wrong?
Yes. We used to fade the button texture, too, and we want to continue to do so. So we should just keep doing what the old code did. I'll attach new images with the disabled state removed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #28)
> Yes. We used to fade the button texture, too, and we want to continue to do so.
> So we should just keep doing what the old code did. I'll attach new images with
> the disabled state removed.

We can do so with the same images, just ignore the disabled state.  IINM this was the exact thing that was being done in the past.  Do you want me to submit a new patch to restore the opacity rule and ditch -moz-image-region?
I think it's better to actually remove the disabled state from the images, so that we don't regress this again the future.
Attachment #380594 - Attachment is obsolete: true
Attachment #380609 - Attachment is obsolete: true
(In reply to comment #24)
> hg did some crazy stuff because the binary image files were both changed and
> renamed, which caused the change not to take affect.

I don't think we care about the file history in this case. For 1.9.1 just remove the old images and add the new ones, fwiw.
Attached patch Followup patchSplinter Review
Followup patch to use the three-state icons.

I think this looks much better now, FWIW.  Thanks for catching my mistake, Dao!
Attachment #380613 - Flags: review?(dao)
Attachment #380613 - Flags: review?(dao) → review+
http://hg.mozilla.org/mozilla-central/rev/59c3caaaddeb
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Attached patch 1.9.1 PatchSplinter Review
Attachment #380623 - Flags: approval1.9.1?
Attachment #380623 - Flags: approval1.9.1? → approval1.9.1+
verified FIXED on builds:

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090601 Minefield/3.6a1pre (.NET CLR 3.5.30729) ID:20090601041706

and

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1pre) Gecko/20090601 Shiretoko/3.5pre (.NET CLR 3.5.30729) ID:20090601044045

and checked on Windows XP builds:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090601 Shiretoko/3.5pre ID:20090601044045

and 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090601 Minefield/3.6a1pre ID:20090601041706
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: