Closed Bug 1055903 Opened 10 years ago Closed 3 years ago

Integrating LayerScope for inspecting composition layers

Categories

(DevTools :: General, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: timdream, Unassigned)

Details

(Keywords: parity-safari)

(Was submitted as https://ffdevtools.uservoice.com/forums/246087/suggestions/6315003) 

https://wiki.mozilla.org/Platform/GFX/LayerScope

LayerScope is a small debug tool from GFX team that gives live updates on composition layers. We should put that into DevTools and make available to front-end developers.

Understanding layers is very important to mobile web development, since having a layer means extra performance boost (if desired), or wasting graphics memory (if undesired). We need this tool to effectively bring Gecko to mobile, and build FxOS Gaia efficiently.

Mobile Safari & Safari already shipped with this feature and supports remote debugging.
I've played with LayerScope a bit. Showing the *content* of the layers might be a bit overkill.

What I had in mind was:
* showing in the timeline (tool coming soon) when layers get cons(des)tructed
* toggling layers outline easily from the devtools
(In reply to Paul Rouget [:paul] (slow to respond. Ping me on IRC) from comment #1)
> * showing in the timeline (tool coming soon) when layers get cons(des)tructed
> * toggling layers outline easily from the devtools

Yeah that works too. As long as people have easy way to tell if a layer exists.
PS specifically, not just outline of every layers but specifically shows different outlines for out-of-main-thread layers. See paragraph 3 or comment 0.
Severity: normal → enhancement
OS: Mac OS X → Unspecified
Priority: -- → P3
Hardware: x86 → Unspecified
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-safari
Whiteboard: [parity-safari]
Product: Firefox → DevTools
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.