81–90 of 360 posts
A clear strategy as to which dev tools will be maintained in the future. Will Firebug and Firefox Dev Tools coexist? What's the plan there? It seems like a duplication of effort from Mozilla.
And as soon as there's a handler for mouse movement, you see nothing else in the flood of onmouse* events.
(Maybe there's an elegant solution to this problem already, but I didn't find any).
This is a big request: Improve "design in the browser" capabilities. i.e. pushing CSS/HTML and maybe JS changes made in Dev Tools back to the source files without manual shenanigans in the middle. I probably waste more time copying CSS / HTML tweak diffs from the browser back into the related source files than anything else with in browser dev tools. Due to the nature of 'losing changes' if I happen to hit refresh or…
Earlier quoted context omitted.
Your comment is somewhat self-contradicting. Baking plugins into firefox will increase Firefox's memory footprint. Plugins are plugins for a reason -- some people will want the functionality and others will not. How would you like to see the API for plugins/add-ons improved?
Dynamically-loaded libraries (.DLL, .so, etc) have been around for decades. A feature can be "baked in" and still loaded (and unloaded) on-demand.
From that, if you can "label" sites or ad styles or script styles that are known to perform poorly, that would be amazing.
I find it difficult to edit code in place and see its change. It'd be nice if when I Right Click > Inspect Element; I can track the changes, and maybe even see side by side comparisons. Most of us have multiple monitors so screen real estate isn't an issue. Maybe even be able to let us launch a new window and edit the currently rendered page would be nice.
Also, the request interface seems kludgy and could be optimized. Having to turn on logging of req/res bodies is an annoying extra step. I feel if the devtools are open it should do that.
Thanks for all your effort. Looking forward to upcoming devtools releases. JSTerm is awesome also!
Hey Paul. First off, thanks for reaching out to the community like this. A few things: Visualized event bindings. Would be awesome to have a visual indicator of event bindings right on the page. Color-coded bounding boxes drawn around elements with a label denoting the event type. Clicking on that box (or label in the case of an element with multiple bindings or nested elements with bindings) would direct you to the…
Yeah, we've been thinking a lot about that lately. Not a priority though (yet?).
> An aggregate repaint view
I filed a platform bug just about that today :) I think it can be done soon.
> An intelligent debugger that would automatically step over certain files
That's interesting. I never thought about this. I like that.
I have to be honest - I find the developer tools a pain: They aren't even close to replacing Firebug, yet they're more obtrusive. So I can't stop using Firebug, and I can't remove the unwanted built-in menu options. So for me personally, what I'd really like to see is either one of: - Match Firebug feature for feature - Allow for the dev tools to be completely removed from the interface Sorry, but it really does come…
Firebug has a "disable built in tools" feature that prevents Inspector from loading already.