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

Favicon partially changes styling depending on tab position and :hover styling

NEW
Unassigned

Status

()

Core
Graphics
P2
normal
9 months ago
8 months ago

People

(Reporter: arni2033, Unassigned)

Tracking

({regression})

Trunk
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

9 months ago
>>>   My Info:   Win7_64, Nightly 53, 32bit, ID 20161219030207 (2016-12-19)
STR_1:
0. Set DPI -> 125% :
 A) Set DPI level -> 125% in your OS   [OR]
 B) Set layout.css.devPixelsPerPx -> 1.25
1. Open new window. Open 3 new tabs with url [1]. close other tabs.
2. Open new selected tab. 
3. Hover mouse over the 3rd tab

> [1] http://www.iana.org/domains/reserved

AR:  Corners of favicon in 1st tab is blue/violet, in 2nd tab - violet, in 3rd tab - red
ER:  Favicon should be drawn the same way regardless of tab position and :hover styling

This is regression from bug 1314133. Regression range:
> https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c04f84afb1bd6b3ea372164012735de6c8f2d582&tochange=b4ade2b0841c5825968f34752d86ee09507a0a9f
(Reporter)

Updated

9 months ago
Component: Untriaged → Graphics
Product: Firefox → Core
(Reporter)

Updated

9 months ago
No longer blocks: 1277113
Do we get the dpi info from widget? And is it still work in gpu process proxy-widget?
Flags: needinfo?(dvander)
Priority: -- → P2
Whiteboard: [gfx-noted]
(In reply to Jerry Shih[:jerry] (UTC+8) from comment #1)
> Do we get the dpi info from widget? And is it still work in gpu process
> proxy-widget?

I think DPI is passed from the widget to the compositor in the CompositorBridgeParent constructor.
Flags: needinfo?(dvander)
You need to log in before you can comment on or make changes to this bug.