>>> 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 . close other tabs. 2. Open new selected tab. 3. Hover mouse over the 3rd tab >  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
Do we get the dpi info from widget? And is it still work in gpu process proxy-widget?
Priority: -- → P2
(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.
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.