Re: New chrome-only API to inject content on top of the page

2014-10-29 Thread Neil

Patrick Brosset wrote:

The discussion [2] that led to the bug was about finding a solution to 
display the devtools highlighter (the box-model overlay you see when 
inspecting a page with the devtools) in a way that would work on 
anything that runs gecko (indeed, prior to this bug, the devtools 
highlighter markup would be appended to one of the page's parent XUL 
node, which didn't work on B2G or Fennec, or with e10s enabled).


What's going to happen to the :-moz-devtools-highlighted pseudoclass?

--
Warning: May contain traces of nuts.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: New chrome-only API to inject content on top of the page

2014-10-29 Thread Patrick Brosset

On 10/29/14, 12:29 PM, Neil wrote:

Patrick Brosset wrote:

The discussion [2] that led to the bug was about finding a solution 
to display the devtools highlighter (the box-model overlay you see 
when inspecting a page with the devtools) in a way that would work on 
anything that runs gecko (indeed, prior to this bug, the devtools 
highlighter markup would be appended to one of the page's parent XUL 
node, which didn't work on B2G or Fennec, or with e10s enabled).


What's going to happen to the :-moz-devtools-highlighted pseudoclass?

We currently still use this pseudoclass for highlighting nodes in XUL 
windows.


The new API only works with HTML windows (where the canvas frame 
exists), and so for XUL windows, we fall back to using the, simpler, red 
outline highlighter we've been using for a while now on b2g/fennec/e10s.

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform