Closed
Bug 495214
Opened 15 years ago
Closed 15 years ago
Refresh tab strip arrows on Windows
Categories
(Firefox :: Theme, defect)
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)
13.44 KB,
patch
|
dao
:
review+
|
Details | Diff | Splinter Review |
3.66 KB,
application/zip
|
Details | |
6.14 KB,
patch
|
dao
:
review+
|
Details | Diff | Splinter Review |
13.99 KB,
patch
|
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
Theme bug for refreshed tab strip arrows on XP and Vista.
Reporter | ||
Updated•15 years ago
|
Whiteboard: [icon-shiretoko][icon-complete]
Reporter | ||
Comment 1•15 years ago
|
||
Reporter | ||
Comment 2•15 years ago
|
||
Reporter | ||
Comment 3•15 years ago
|
||
Reporter | ||
Comment 4•15 years ago
|
||
Reporter | ||
Comment 5•15 years ago
|
||
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.
Comment 6•15 years ago
|
||
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.
Reporter | ||
Comment 7•15 years ago
|
||
sorry, hit layer had opacity problem, fixed
Attachment #380093 -
Attachment is obsolete: true
Reporter | ||
Comment 8•15 years ago
|
||
the -aero are both a darker blue, and the xp icons use a brighter blue, they should all match their counterparts now.
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → ehsan.akhgari
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•15 years ago
|
||
Attachment #380121 -
Flags: review?(dao)
Assignee | ||
Comment 10•15 years ago
|
||
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)
Comment 11•15 years ago
|
||
(this has my pre-approval to land on mozilla-central once reviewed, please nominate for a191 when that happens)
Comment 12•15 years ago
|
||
(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 13•15 years ago
|
||
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)
Assignee | ||
Comment 14•15 years ago
|
||
(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]
Assignee | ||
Comment 15•15 years ago
|
||
Addressed comment 13 for now...
Attachment #380154 -
Attachment is obsolete: true
Reporter | ||
Updated•15 years ago
|
Attachment #380452 -
Flags: review?(dao)
Comment 16•15 years ago
|
||
Comment on attachment 380452 [details] [diff] [review] Patch (v2.1) needs fixed image files
Attachment #380452 -
Flags: review?(dao) → review-
Reporter | ||
Comment 17•15 years ago
|
||
Attachment #380091 -
Attachment is obsolete: true
Attachment #380092 -
Attachment is obsolete: true
Attachment #380094 -
Attachment is obsolete: true
Attachment #380097 -
Attachment is obsolete: true
Comment 18•15 years ago
|
||
Ehsan, while you're at it, care to rename the files from arrow-start and arrow-end to arrow-left and arrow-right?
Assignee | ||
Updated•15 years ago
|
Whiteboard: [icon-shiretoko][icon-needed] → [icon-shiretoko][icon-complete]
Assignee | ||
Comment 19•15 years ago
|
||
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 20•15 years ago
|
||
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 21•15 years ago
|
||
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.
Assignee | ||
Comment 22•15 years ago
|
||
(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?
Assignee | ||
Comment 23•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/543dfafa466a
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.6a1
Assignee | ||
Comment 24•15 years ago
|
||
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>
Assignee | ||
Comment 25•15 years ago
|
||
Branch patch without renaming the images.
Attachment #380609 -
Flags: approval1.9.1?
Comment 26•15 years ago
|
||
(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?
Updated•15 years ago
|
Attachment #380609 -
Flags: approval1.9.1?
Assignee | ||
Comment 27•15 years ago
|
||
(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?
Comment 28•15 years ago
|
||
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.
Updated•15 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 29•15 years ago
|
||
(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?
Comment 30•15 years ago
|
||
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
Comment 31•15 years ago
|
||
(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.
Assignee | ||
Comment 32•15 years ago
|
||
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)
Updated•15 years ago
|
Attachment #380613 -
Flags: review?(dao) → review+
Assignee | ||
Comment 33•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/59c3caaaddeb
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 34•15 years ago
|
||
Attachment #380623 -
Flags: approval1.9.1?
Updated•15 years ago
|
Attachment #380623 -
Flags: approval1.9.1? → approval1.9.1+
Comment 35•15 years ago
|
||
Comment on attachment 380623 [details] [diff] [review] 1.9.1 Patch a191=beltzner
Assignee | ||
Comment 36•15 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/4df4434bc10a
Keywords: fixed1.9.1
Comment 37•15 years ago
|
||
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.
Description
•