Closed
Bug 887368
Opened 11 years ago
Closed 11 years ago
social notification icon not sized correctly on a retina screen
Categories
(Firefox Graveyard :: SocialAPI, defect)
Tracking
(firefox24+ verified, firefox25 verified)
VERIFIED
FIXED
Firefox 25
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(3 files, 1 obsolete file)
47.48 KB,
image/png
|
Details | |
790 bytes,
patch
|
mixedpuppy
:
review+
Gavin
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
48.27 KB,
image/png
|
Details |
Forcing the height of #social-notification-icon > .toolbarbutton-icon to 16px fixes the issue but I haven't found why this is needed (yet). The other icon that doesn't look right on the attached screenshot is already handled in bug 886816.
Comment 1•11 years ago
|
||
possibly related to bug 886859?
Assignee | ||
Comment 2•11 years ago
|
||
(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #1) > possibly related to bug 886859? Maybe. But the size of the icon is totally reasonable when I move the window to my external (non-retina) monitor.
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Florian Quèze [:florian] [:flo] from comment #0) > Forcing the height of #social-notification-icon > .toolbarbutton-icon to > 16px fixes the issue This is what I'm doing in this patch. > but I haven't found why this is needed (yet). Now I know. The height set on the toolbarbutton isn't propagated to the xul image, which uses the natural height of the image file. The image file for the indexedDb notification I had on my screenshot has a height of 16px on a normal screen and 32px on a retina one, as this code indicates: http://mxr.mozilla.org/mozilla-central/source/browser/themes/osx/browser.css#3091 3091 .indexedDB-notification-icon, 3092 #indexedDB-notification-icon { 3093 list-style-image: url(chrome://global/skin/icons/question-16.png); 3094 } 3095 @media (min-resolution: 2dppx) { 3096 .indexedDB-notification-icon, 3097 #indexedDB-notification-icon { 3098 list-style-image: url(chrome://global/skin/icons/question-32.png); 3099 } 3100 } I'll attach soon another patch that's IMHO cleaner, but also slightly riskier if my understanding of the situation is partial or mistaken.
Assignee: nobody → florian
Attachment #768300 -
Flags: review?(mixedpuppy)
Assignee | ||
Comment 4•11 years ago
|
||
The approach I'm taking here assumes that the size constraints set on the toolbarbutton isn't propagated to the xul image, so we should set the size on the xul image directly. This removes a line from my patch for bug 887314 that's no longer necessary, and likely does part of what was intended for bug 886859.
Attachment #768301 -
Flags: review?(mixedpuppy)
Assignee | ||
Comment 5•11 years ago
|
||
Comment on attachment 768301 [details] [diff] [review] Alternative patch This alternative patch isn't correct, we need the width and height set on .notification-anchor-icon directly, as the notifications attached to the location bar are directly xul:image nodes.
Attachment #768301 -
Attachment is obsolete: true
Attachment #768301 -
Flags: review?(mixedpuppy)
Updated•11 years ago
|
Attachment #768300 -
Flags: review?(mixedpuppy) → review+
Updated•11 years ago
|
status-firefox24:
--- → affected
status-firefox25:
--- → affected
Assignee | ||
Comment 6•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/3c4bbca40720
Comment 7•11 years ago
|
||
What caused this bug?
Comment 8•11 years ago
|
||
(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #7) > What caused this bug? bug 809085, I added permissions support. There are a few places I have not handled retina correctly.
Comment 9•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/3c4bbca40720
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 25
Updated•11 years ago
|
Attachment #768300 -
Flags: approval-mozilla-aurora+
Updated•11 years ago
|
tracking-firefox24:
--- → +
Assignee | ||
Comment 10•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/6e574b2c6b8a
Comment 11•11 years ago
|
||
Matt, can you please verify this is fixed in Firefox 24 and 25?
Keywords: verifyme
QA Contact: mwobensmith
Comment 12•11 years ago
|
||
Pardon me for asking, but my icons don't resemble the screenshot in this bug, so I cannot reproduce the behavior pre- or post-patch in order to verify. I can also see a Twitter icon in this bug's screenshot, but I can't find instructions on how to get Twitter added via the Social API. Can someone tell me how to reproduce this bug so that I can verify it fixed on my Retina Mac? Much appreciated, and thanks in advance.
Comment 13•11 years ago
|
||
(In reply to Matt Wobensmith from comment #12) > Created attachment 779828 [details] > Screenshot of buttons in my build > > Pardon me for asking, but my icons don't resemble the screenshot in this > bug, so I cannot reproduce the behavior pre- or post-patch in order to > verify. > > I can also see a Twitter icon in this bug's screenshot, but I can't find > instructions on how to get Twitter added via the Social API. > > Can someone tell me how to reproduce this bug so that I can verify it fixed > on my Retina Mac? Much appreciated, and thanks in advance. The twitter icon is from a mockup provider. It is better to use the demo provider as it does a geo location request when its sidebar loads. http://mixedpuppy.github.io/socialapi-demo/
Comment 14•11 years ago
|
||
Thanks Shane. I still can't see the blue info icon that is visible in the original screenshot. What I *did* see was the geolocation icon appear during the permission request. In the pre-patch build, the icon appeared stretched vertically (much like the blue info icon in this bug) and then disappear once permission was granted. On the post-patch build, the same icon appears normal and undistorted. Is this anything close to what we're looking for?
Comment 15•11 years ago
|
||
Yes. The stretched appearance would have affected any of the permission icons.
Comment 16•11 years ago
|
||
Perfect, thank you Shane. I confirmed the issue on FF25 2013-06-26. I verified the fix on FF24, FF25 2013-07-19.
Updated•5 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•