Closed
Bug 1410498
Opened 7 years ago
Closed 7 years ago
Visual appearance of autoscroll indicator has regressed, doesn't match photon specs
Categories
(Toolkit :: Themes, defect, P2)
Toolkit
Themes
Tracking
()
VERIFIED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox57 | --- | unaffected |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | verified |
firefox61 | --- | verified |
People
(Reporter: botond, Assigned: shorlander)
References
Details
(Keywords: regression, uiwanted)
Attachments
(5 files, 1 obsolete file)
(deleted),
image/png
|
Details | |
(deleted),
image/png
|
Details | |
(deleted),
image/png
|
Details | |
(deleted),
patch
|
dao
:
review+
lizzard
:
approval-mozilla-release-
|
Details | Diff | Splinter Review |
(deleted),
image/png
|
Details |
In recent nightlies, the visual appearance of the autoscroll indicator has changed on Linux, and it looks pretty bad.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Reporter | ||
Comment 4•7 years ago
|
||
Based on bug 1389462, it looks like it was an intentional change. I think that's unfortunate - to me, the previous one looks polished, while the new one looks cartoonish - but ok.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Comment 5•7 years ago
|
||
I don't think you have to close it as invalid. You can ask UX team for review of the result of that work if you think the visual style of the new one is an actual regression.
Reporter | ||
Comment 6•7 years ago
|
||
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #5)
> You can ask UX team for
> review of the result of that work if you think the visual style of the new
> one is an actual regression.
It looks to me like the new design got UX approval in bug 1389462 comment 3.
Comment 7•7 years ago
|
||
Correct, and it looks really good on the SVG file, but maybe not as great in the miniature like you presented on the screenshot.
The fact that our UX team accepted a proposal doesn't mean it cannot be revised based on the result :)
Reporter | ||
Comment 8•7 years ago
|
||
Ok, fair enough. Stephen, would it be possible for UX to review the result of the changes made in bug 1389462, as suggested in comment 7?
Status: RESOLVED → REOPENED
Flags: needinfo?(shorlander)
Resolution: INVALID → ---
I think it looks like it should for iOS:
>On iOS, use 3px strokes for the foundation and 2px strokes for the details
And should look like this :
>When lines principally shape your icon, use a 2px stroke for the foundation and a 1px line for extra details.
http://design.firefox.com/photon/visuals/iconography.html#shape
Compared to, for example "Reload" button, this looks bad.
Updated•7 years ago
|
Component: XUL Widgets → Themes
Updated•7 years ago
|
status-firefox57:
--- → unaffected
status-firefox58:
--- → affected
Keywords: uiwanted
Priority: -- → P2
Assignee | ||
Comment 11•7 years ago
|
||
The change with regards to the styling is the direction we want to go. Something seems off with the scaling of the SVG thought.
Assignee: nobody → shorlander
Flags: needinfo?(shorlander)
Comment 12•7 years ago
|
||
(In reply to Stephen Horlander [:shorlander] from comment #11)
> The change with regards to the styling is the direction we want to go.
> Something seems off with the scaling of the SVG thought.
Could you please elaborate how the scaling is off / what we should fix here?
Flags: needinfo?(shorlander)
Assignee | ||
Comment 13•7 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #12)
> (In reply to Stephen Horlander [:shorlander] from comment #11)
> > The change with regards to the styling is the direction we want to go.
> > Something seems off with the scaling of the SVG thought.
>
> Could you please elaborate how the scaling is off / what we should fix here?
I still need to dig into exactly what's going on, but the autoscroll image should be following the same 2px and 1px line rule as the rest of the icons (http://design.firefox.com/photon/visuals/iconography.html#shape). It looks like it's scaled too large though.
Flags: needinfo?(shorlander)
Comment 14•7 years ago
|
||
(In reply to Stephen Horlander [:shorlander] from comment #13)
> I still need to dig into exactly what's going on, but the autoscroll image
> should be following the same 2px and 1px line rule as the rest of the icons
> (http://design.firefox.com/photon/visuals/iconography.html#shape). It looks
> like it's scaled too large though.
Any updates here?
Flags: needinfo?(shorlander)
Updated•7 years ago
|
Comment 15•7 years ago
|
||
As far as I can tell this is just because the icon is drawn on a 16x16 canvas like the toolbar icons, but displayed at 28x28. If the SVG is modified to use a 28x28 canvas it looks a lot better.
Comment hidden (mozreview-request) |
Comment 17•7 years ago
|
||
Oops, forgot to comment. So the above patch is just converting the icon to being drawn in a 28x28 canvas as I mentioned in comment #15. Discussed with shorlander on IRC and the arrows might need adjusting slightly since the diagonal angle they are drawn at means that perceptually they are slightly thinner than their specified 1px.
Comment 18•7 years ago
|
||
Update description & platforms since this isn't exclusive to Linux (tested on Windows).
OS: Linux → All
Hardware: x86_64 → All
Summary: Visual appearance of autoscroll indicator has regressed on Linux → Visual appearance of autoscroll indicator has regressed, doesn't match photon specs
Assignee | ||
Comment 19•7 years ago
|
||
I looked into this a bit. I decided to flip the visual emphasis from the circle to the arrows and made it 32 x 32 to conform to our icon guidelines.
Flags: needinfo?(shorlander)
Attachment #8954494 -
Flags: review?(dao+bmo)
Assignee | ||
Comment 20•7 years ago
|
||
Updated•7 years ago
|
Attachment #8941938 -
Attachment is obsolete: true
Comment 21•7 years ago
|
||
Would be nice to uplift this to beta.
Updated•7 years ago
|
Attachment #8954494 -
Flags: review?(dao+bmo) → review+
Comment 22•7 years ago
|
||
Dão, does the .autoscroll CSS in the global.css files need to be updated as well to reflect the new dimensions ?
Flags: needinfo?(dao+bmo)
Comment 23•7 years ago
|
||
Nevermind, I was looking at an old version of the CSS.
Flags: needinfo?(dao+bmo)
Updated•7 years ago
|
Keywords: checkin-needed
Comment 24•7 years ago
|
||
Pushed by csabou@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/c9d9579b0629
Fix autoscroll image. r=dao
Keywords: checkin-needed
Comment 25•7 years ago
|
||
Comment on attachment 8954494 [details] [diff] [review]
fix-autoScroll-image.patch
Approval Request Comment
[Feature/Bug causing the regression]: bug 1389462
[User impact if declined]: autoscroll image looks bad
[Is this code covered by automated tests?]: no
[Has the fix been verified in Nightly?]: not yet
[Needs manual test from QE? If yes, steps to reproduce]: no
[List of other uplifts needed for the feature/fix]: none
[Is the change risky?]: no
[Why is the change risky/not risky?]: simple image swap
[String changes made/needed]: none
Attachment #8954494 -
Flags: approval-mozilla-beta?
Comment 26•7 years ago
|
||
bugherder |
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
Comment on attachment 8954494 [details] [diff] [review]
fix-autoScroll-image.patch
Since the beta to release merge was today, just moving the flag to m-r.
Attachment #8954494 -
Flags: approval-mozilla-beta? → approval-mozilla-release?
Comment on attachment 8954494 [details] [diff] [review]
fix-autoScroll-image.patch
Though this seems like a small change, I'd rather let it ride the trains with 60, unless you have strong objections. We are about to build the release candidate on Monday so this is pretty last minute.
Attachment #8954494 -
Flags: approval-mozilla-release? → approval-mozilla-release-
Updated•7 years ago
|
Updated•7 years ago
|
Flags: qe-verify+
Comment 29•7 years ago
|
||
I managed to reproduce the bug using an older version of Nightly (2017-10-20) on Windows 10 x64.
I retested everything on latest Nightly 61.0a1 and beta 60.0b5 on Windows 10 x 64, macOS 10.13 and Ubuntu 16.04 x64 and the bug is not reproducing anymore.
You need to log in
before you can comment on or make changes to this bug.
Description
•