<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/12/2015 21:43, Jeff Griffiths wrote:<br>
<blockquote
cite="mid:CAKZskdb1-ZXwDymSpp3J0RqKAUfKyZdUhrX_JSmX5P24Bk_vOA@mail.gmail.com"
type="cite">
<pre wrap="">If you're using DOM Inspector as an indispensable part of your
workflow developing for Firefox Desktop I'd like to hear about your
use case and in particular what is lacking in the Browser Toolbox.
</pre>
</blockquote>
Although Browser Toolbox is getting a lot better, there's a few
issues that make me want to switch back to DOMI now and again (I'll
admit, I haven't got around to looking for or filing bugs for
these):<br>
<ul>
<li>It doesn't cope with multiple windows. Sometimes I want to be
able to inspect/debug a detached Hello conversation window, or
just switch the toolbox to a different browser window than the
one that's was originally open.</li>
<li>It has improved, but still isn't brilliant at coping with
opening/closing of windows/sub-browsers. For example, it
frequently doesn't pick up changes properly if we inspect the
Hello conversation window, close it and then re-open it.<br>
</li>
<li>We don't seem to be able to dynamically change user-agent css
- I thought that was possible with DOMI, though I could be wrong
(this is will probably hurt us on Hello soon as we've switched
to a system add-on).<br>
</li>
<li>Running two instances against two running instances of FF is
hard. The other day I was trying to figure out why stuff wasn't
working, and so wanted to compare the css styles with one of a
"good" build. That would have been easy with DOMI, but not so
with toolbox. Admittedly I've only ever wanted to do this once
so far.</li>
</ul>
<p>Mark<br>
</p>
</body>
</html>