Open Bug 1301535 Opened 8 years ago Updated 3 days ago

The eyedropper doesn't pick colors correctly on the expanded content area when expanding content area after launch it

Categories

(DevTools :: Inspector, defect, P2)

Product:
DevTools
Component:
Inspector
Version:
36 Branch
Type:
defect

Tracking

(firefox48 wontfix, firefox49 wontfix, firefox50 wontfix, firefox51 wontfix, firefox52 fix-optional, firefox53 fix-optional, firefox54 wontfix, firefox56 wontfix, firefox57 fix-optional)

Tracking Flags:
Tracking Status
firefox48 --- wontfix
firefox49 --- wontfix
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 --- fix-optional
firefox53 --- fix-optional
firefox54 --- wontfix
firefox56 --- wontfix
firefox57 --- fix-optional

People

(Reporter: magicp.jp, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression) 

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20160908030434

Steps to reproduce:

1. Start Nightly with normal browser window (not full screen and maximize)
2. Go to any sites
3. Run eyedropper
4. Full Screen (F11)
5. Mouse over the expanded content area


Actual results:

The eyedropper doesn't pick colors correctly on the expanded content area when expanding content area after launch it


Expected results:

The eyedropper works on the expanded content area even if expanding content area.
Has STR: --- → yes
status-firefox48: --- → wontfix
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox51: --- → affected
Component: Untriaged → Developer Tools: Inspector
OS: Unspecified → All
Hardware: Unspecified → All
Inspector bug triage (filter on CLIMBING SHOES).
Priority: -- → P2
Could be considered as a regression from the old eyedropper migration.
Keywords: regression
Too late for a fix for 49. We could still potentially take a patch for 50 though.
status-firefox49: affected → wontfix
status-firefox50: affected → fix-optional
status-firefox54: --- → affected
Gabriel, is this likely to be fixed/uplifted, or should we classify this as a backlog bug, given the lack of fixes in recent releases?
Flags: needinfo?(gl)
Too late for 54, let's see if we can fix it in 55.
status-firefox54: affected → wontfix
status-firefox55: --- → affected
Backlog bug.
Flags: needinfo?(gl)
Product: Firefox → DevTools
Severity: normal → S3
status-firefox55: wontfix → ---
You need to log in before you can comment on or make changes to this bug.