Sounds a lot like it! I'll follow that bug and contribute my findings.
On Wednesday, 15 November 2017 22:42:51 UTC+1, Kris Maglione wrote:
> This is probably bug 1408996.
>
> On Wed, Nov 15, 2017 at 01:34:44PM -0800, Jip de Beer wrote:
> >This simple web extension used to wo
This simple web extension used to work on FF51 and still works on Google Chrome.
But it no longer works reliably on FF57 when loading the content script for
https://vk.com/.
I get the following error:
ReferenceError: Awesomplete is not defined contentscript.js:464:5
The extension adds an autoco
.tech.layout:
https://groups.google.com/forum/#!topic/mozilla.dev.tech.layout/MClwXlzk5qM
On Tuesday, 19 April 2016 15:49:40 UTC+2, Gijs Kruitbosch wrote:
> 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
> > wit
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
he display-list? I'd like to
override this optimization and include all elements within the document instead.
> Op 16 apr. 2016 om 01:45 heeft Botond Ballo het volgende
> geschreven:
>
>> On Fri, Apr 15, 2016 at 4:32 AM, Jip de Beer wrote:
>> Thanks for the reply. M
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
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
document.
On Thursday, 14 April 2016 18:03:11 UTC+2, Boris Zbarsky wrote:
> 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
> durin
#x27;t contain any information about z-order. How can I know
which nodes are in front of other nodes?
On Saturday, 9 April 2016 09:05:09 UTC+2, Jip de Beer wrote:
> Hi Daniel,
>
> Thanks for the info. Thanks to your instructions I was able to find the
> Layout Debugger Jeff mention
how need to make the Frame Tree accessible to addons or
JavaScript. Sounds more complicated then dumping to the terminal.
On Saturday, 9 April 2016 01:56:20 UTC+2, Daniel Holbert wrote:
> On 04/08/2016 02:55 PM, Daniel Holbert wrote:
> > On 04/08/2016 10:38 AM, Jip de Beer wrote:
> >
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
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
12 matches
Mail list logo
