Closed
Bug 690064
Opened 13 years ago
Closed 11 years ago
Show borders of compositing layers
Categories
(Core :: Graphics, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 860146
People
(Reporter: david.b.calhoun, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
690.99 KB,
image/png
|
Details | |
22.14 KB,
patch
|
Details | Diff | Splinter Review | |
5.51 KB,
patch
|
Details | Diff | Splinter Review | |
15.94 KB,
patch
|
Details | Diff | Splinter Review | |
242.74 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Steps to reproduce: It would be nice to be able to show layer compositing layers for debugging purposes. Safari and Chrome have similar functionality: Safari 1. Open a terminal 2. $ defaults write com.apple.Safari \IncludeInternalDebugMenu 1 3. Open (or restart) Safari 4. Debug -> Show Compositing Borders Chrome 1. Type the following in the address bar: about:flags 2. "Composited render layer borders" -> Enable Actual results: No options to see compositing layers! Expected results: There should be a flag in about:config to show compositing layers, and possibly the redraws (as Safari shows). I.e: layers.acceleration.draw-borders
Updated•13 years ago
|
Severity: normal → enhancement
Component: General → Developer Tools
QA Contact: general → developer.tools
Updated•13 years ago
|
Component: Developer Tools → Graphics
Product: Firefox → Core
QA Contact: developer.tools → thebes
Version: 9 Branch → unspecified
Comment 1•13 years ago
|
||
Agreed. This would make layers debugging easier. Maybe even a candidate menu item for bug 692867? I would even consider doing a patch myself to help debugging work with mobile opengl layers.
Updated•13 years ago
|
Blocks: opengl-mobile
It would also be really useful to draw thebeslayerbuffers unrotated. There was some testing code in bug 570294 that was heading towards this (we were calling it "LayersSpy"), but that code might not be very helpful here.
Comment 3•13 years ago
|
||
Found a bug while working on this. It assumes that unsigned int are 32-bit which isn't true everywhere. http://mxr.mozilla.org/mozilla-central/source/gfx/layers/opengl/LayerManagerOGL.cpp#583
Comment 4•13 years ago
|
||
I've implemented this in the form of an overlay. I'm not sure I like it as-it. The color is the layer type. In this case green is an Image Layer while purple is a thebes layers. Should I just make it a border?
We need to be able to visually distinguish different layers of the same type. As an extension I'd like to be able to tell which parts of layers are getting invalidated/repainted, so let's at least have a design for that.
Comment 6•13 years ago
|
||
Comment 7•13 years ago
|
||
Updated•13 years ago
|
Attachment #566187 -
Attachment is patch: true
Comment 8•13 years ago
|
||
Comment 9•13 years ago
|
||
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #5) > We need to be able to visually distinguish different layers of the same type. > We have overlapping layers so simply showing the border wont be enough. I'm not sure what the best visual representation for that could be. I'm going to think about it some more. Any suggestion? > As an extension I'd like to be able to tell which parts of layers are > getting invalidated/repainted, so let's at least have a design for that. That's a good idea.
(In reply to Benoit Girard (:BenWa) from comment #9) > (In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #5) > > We need to be able to visually distinguish different layers of the same type. > > We have overlapping layers so simply showing the border wont be enough. I'm > not sure what the best visual representation for that could be. I'm going to > think about it some more. Any suggestion? Showing the borders wouldn't be enough in all cases but it's still the best option I can think of.
Comment 11•13 years ago
|
||
I made another experiment. It flashes each layer out for 1 second. It gives you a good impression of what the layers. The color are the layer type: Purple -> Thebes, Green -> Image. http://dl.dropbox.com/u/10523664/VID_20111103_181638.3gp I think we will want layer border anyways. Any though on this experiment?
It's OK but I think borders would be better.
Comment 13•13 years ago
|
||
Here's my latest attempt. Perhaps the border width should be reduced.
Comment 14•13 years ago
|
||
I think we should use different colors and transparency to give some indication of z-order and superposition of different layers with the same border.
Comment 15•13 years ago
|
||
I'm currently using colors to tell the layer type. Purple is thebes, green is image (not pictured). If we think that superposition information is more important then layer type we could use colors for that instead.
Comment 16•13 years ago
|
||
Comment on attachment 566186 [details] [diff] [review] Part 1: Refactor FPS code into new LayerDebugOGL Asking Jeff for review since he worked on the original FPS code.
Attachment #566186 -
Flags: review?(jmuizelaar)
Updated•13 years ago
|
Attachment #566187 -
Flags: review?(jmuizelaar)
Updated•13 years ago
|
Keywords: dev-doc-needed
(In reply to Robert O'Callahan (:roc) (Mozilla Corporation) from comment #5) > As an extension I'd like to be able to tell which parts of layers are > getting invalidated/repainted, so let's at least have a design for that. +1 <3. I'd also love something like this to show special-case-y optimizations that are being hit, like pre-rendered transformed frames and animations/transitions that are asyncified.
Updated•12 years ago
|
Attachment #566186 -
Flags: review?(jmuizelaar)
Updated•12 years ago
|
Attachment #566187 -
Flags: review?(jmuizelaar)
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•