On Wed, Apr 20, 2016 at 5:50 AM, Jip de Beer wrote:
> Thanks. I'm aware that it's a privileged API. It seemed Botond was offering a
> workaround.
In my testing, I used it in the Browser Console (as opposed to the Web
Console), which can access privileged APIs.
As you were the one who brought up
Thanks. I'm aware that it's a privileged API. It seemed Botond was offering a
workaround.
Anyhow, because of all your help I was able to dump the Frame Tree (not in real
time). But I also learned the frame tree doesn't contain all the information I
need. Especially the z-order information.
The
On 19/04/2016 14:41, Jip de Beer wrote:
I followed your steps exactly and uses this code to add a canvas on a page with
jQuery:
var myCanvas = document.createElement('canvas');
var width = $(document).width()
myCanvas.width = width;
var height = $(document).height()
myC
I followed your steps exactly and uses this code to add a canvas on a page with
jQuery:
var myCanvas = document.createElement('canvas');
var width = $(document).width()
myCanvas.width = width;
var height = $(document).height()
myCanvas.height = height;
var ctx = myCanvas.g
Hi Botond thanks for replying,
I just checked and calling drawWindow() doesn't output the entire page in the
display-list dumps. It's as if this operation doesn't trigger the same things a
regular render operation does.
But your reply got me thinking. If I can force Firefox to always render the
Great to hear you got this working! I'll carefully follow your steps and see if
I can get it to work too.
The downside of this approach seems that I can't easily filter out the dumps of
the entire page. I'm only interested in the dumps from the whole page, not the
ones from the viewport. But th
On Mon, Apr 18, 2016 at 2:06 PM, Jip de Beer wrote:
> I just checked and calling drawWindow() doesn't output the entire page in the
> display-list dumps. It's as if this operation doesn't trigger the same things
> a regular render operation does.
It worked for me. Here's what I did specifically
Hi Botond thanks for replying,
I just checked and calling drawWindow() doesn't output the entire page in the
display-list dumps. It's as if this operation doesn't trigger the same things a
regular render operation does.
But your reply got me thinking. If I can force Firefox to always render the
On Fri, Apr 15, 2016 at 4:32 AM, Jip de Beer wrote:
> Thanks for the reply. My problem with display lists is that they only contain
> this information about nodes within the viewport. I'm interested in all nodes
> that take up space within the document.
>
> I know Firefox can calculate the neces
Thanks for the reply. My problem with display lists is that they only contain
this information about nodes within the viewport. I'm interested in all nodes
that take up space within the document.
I know Firefox can calculate the necessary information for nodes outside of the
viewport because I
On 4/14/16 10:52 AM, Jip de Beer wrote:
The Frame Dump doesn't contain any information about z-order.
That information is not stored in the frame tree, really. It's computed
during display list construction.
How can I know which nodes are in front of other nodes?
The answer, in general,
Unfortunately Dump -> Frames using the Layout Debugger doesn't give me the
information I'm looking for.
I would like to access the following information about all visible DOM nodes
(nodes that take up space in the document):
- z-order
- position
- dimensions
The Frame Dump doesn't contain any i
Hi Daniel,
Thanks for the info. Thanks to your instructions I was able to find the Layout
Debugger Jeff mentioned. I forgot to add that I did add the debug option in
.mozconfig when building the nightly.
This was the full .mozconfig file
# Define where build files should go. This places them in
On 04/08/2016 02:55 PM, Daniel Holbert wrote:
> On 04/08/2016 10:38 AM, Jip de Beer wrote:
>> I didn't manage to dump the Frame Tree using lldb... I followed these guides:
> [...]
>> I tried with Firefox, FirefoxDeveloperEdition and the nightly build (ran
>> lldb from Terminal as well as Xcode).
>
On 04/08/2016 10:38 AM, Jip de Beer wrote:
> I didn't manage to dump the Frame Tree using lldb... I followed these guides:
[...]
> I tried with Firefox, FirefoxDeveloperEdition and the nightly build (ran lldb
> from Terminal as well as Xcode).
> I was able to attach lldb to the browser, but not
On Friday, 8 April 2016 20:06:19 UTC+2, Jeff Muizelaar wrote:
> Check out
> https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Layout_Debugger.
> I expect it gets the information that you're looking for.
>
> -Jeff
>
> On Fri, Apr 8, 2016 at 1:38 PM, Jip de Beer wrote:
> > Hi all,
> >
>
Check out
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Layout_Debugger.
I expect it gets the information that you're looking for.
-Jeff
On Fri, Apr 8, 2016 at 1:38 PM, Jip de Beer wrote:
> Hi all,
>
> I would like to inspect the Frame Tree (or Render Tree:
> http://www.html5rocks
Hi all,
I would like to inspect the Frame Tree (or Render Tree:
http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/#Render_tree_construction)
in real time while browsing with Firefox.
I first tried to access this tree with JavaScript or a browser addon. It seems
that this informa
18 matches
Mail list logo
