If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Refresh button is too big (HiDPI)

RESOLVED INCOMPLETE

Status

()

Firefox
Theme
RESOLVED INCOMPLETE
25 days ago
20 days ago

People

(Reporter: fwrk, Unassigned)

Tracking

({dpi})

55 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

25 days ago
Created attachment 8903149 [details]
2shWB4ujQl2k-PCB-lv6rA[1].png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170814072924

Steps to reproduce:

Good day, Mozilla team!

Two weeks ago I updated my Firefox (32bit) to 55.0.2 (oh, why?!) and 
- Refresh button
became broken (too big).

https://prnt.sc/g9oa0k
https://prnt.sc/g9o446

I use Win 7 x64 with screen Hi-DPI scale factor of 151% https://prnt.sc/g9obiw (not default 100%, nor semi-default 150% or 200%)

Firefox 54.0.1 was fine.

As you see, other default buttons (and stop button too) is OK, but not the refresh button.
Fix this please.



Actual results:

Refresh button in address bar is too big. (HiDPI)


Expected results:

The button must have the same normal size as all of other buttons.

Updated

25 days ago
Component: Untriaged → Theme
Keywords: dpi

Comment 1

20 days ago
Does this happen on a clean Firefox profile as well?
Flags: needinfo?(fwrk)
(Reporter)

Comment 2

20 days ago
It's strange, but this bug disappeared when I updated to 55.0.3.

But this bug "was stable" while my FF was 55.0.2.
Clean profile? Not exact, I have some extensions enabled, but not too many ones.

Well, may be this report still can help FF team in future.

Thanks for paying attention!
Good luck!
Flags: needinfo?(fwrk)

Comment 3

20 days ago
OK, while we don't know what caused it, marking as incomplete. We can reopen if this resurfaces / we have more details about what causes it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 20 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.