Tab group: one process per group. Kill one group kill all the tabs within the group. Make most extensions per group instead of browser wide to improve isolation and security.
It's a natural evolution from one process per tab.
Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
341–350 of 360 posts
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#342Earlier quoted context omitted.
+1. I can't even add an element directly in the Chrome dev tools - you can only edit an existing elements HTML and append something after it. My kingdom for a '+' button.
You can, sort of. Right click on an element and choose "edit as HTML" and you can add whatever you want, granted it offers no reasonable formatting, its just a wall of text, not even tabs / line breaks. It is also broken in that when you do this Chrome rebuilds all the sub elements of what your editing so if there were event hooks or anything like that on the elements they will be gone.
It really seems like you didn't read my post before you replied to it.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#343Add better support for keyboard shortcuts. I use firefox every day and I still prefer it to chrome because it has better keyboard shortcuts, but they could be better still. 1. I can't disable Ctrl-P/Cmd-P that maps to print screen. I use emacs and this conflicts with many shortcuts that I am used to using. The print dialog takes a full second to display. I haven't had a printer in 8 years. 2. Firefox gives webpages m…
Ad. 1: Install keyconfig: http://mozilla.dorando.at/keyconfig.xpi (more here: http://forums.mozillazine.org/viewtopic.php?t=72994). I've been using it for ages.
Ad. 3: what do you mean? To toggle between zoom-text-only and standard zoom? Unfortunately I don't know a way to do it either.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#344Not related to devtools but please make the facebook addon or plugin or whatever removable
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#345This 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…
I'm the author of http://tin.cr , it tries to solve this exact problem for Chrome Devtools. (someone else mentioned this in this thread). I've spent some time thinking about the problem. In an ideal world a standardized protocol to push changes to a server would be awesome. I think it's unrealistic though to expect widespread adoption especially for existing frameworks to add code just for doing this. For example, ha…
When I try to install the extension I get the following error: "This application is not supported on this computer. Installation has been disabled." I have a Thinkpad T420s running windows 8 with Chrome Version 25.0.1364.152 m, any idea what's not compatible?
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#346I'm a bit late in commenting here, but would love Firefox to do one thing with script debugging. A lot of scripts are written unindented, without spaces, and may be obfuscated to save size and for other obvious reasons. But that makes script debugging very difficult in the browser. A feature to properly indent them, and possibly unobfuscate them 'live'
in the debugger will be great ! Not sure how difficult would that be ...
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#347This is probably too late...
Right clicking an element, you have "Copy CSS Path". I want the same thing for JS. Something where copy/paste gives me "getElementById()" for the element or some other way to uniquely identify that element in JS. I can then easily paste it into the Console and get to work.
Cheers!
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#348fix issue 201011 (https://bugzilla.mozilla.org/show_bug.cgi?id=201011)
Some years ago I really wanted to change some firefox keybindings but found to my dismay that they were broken. I then used the keyconfig extension which worked really well until a firefox upgrade broke it - haven't tried it again. Surely something like this should be in firefox core...
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#349Honestly, the absolute best thing you could do for any dev, is lighten the footprint FF currently has on my ram, and continue to improve the api for add-ons/plugins. The more stable, extensible and fast FireFox is, the more useful I will find it for development. But if more kludge is added to it, and it continues to get slower/bigger, the less likely I am to continue to use it, regardless of what amazing plugins are…
We already have a team working on memory consumption (and we already made some gigantic progress). We also have a team working on improving addons APIs (see the new builin SDK). We are also looking at existing extensions.
What about an easy way to redistribute customized versions of Firefox? What im thinking about is something like a software pack or plugin bundles, similar to ninite. Very much like the spf-13 vim distribution. Or like some of the bundled eclipse distributions, like PyDev or Aptana. It's a batteties included idea.
There are a lot of cool plugins, but new users don't always know what to get. But if if it was easy to fork Firefox and add some plugins and redistribute it in whatever forums or communities they prefer, that would be cool.
So there may end up being a Firefox for reddit, for image processing, for web design, for web dev, etc.
Re: Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?
#350Earlier quoted context omitted.
For what it's worth, it's a warning, not an error. And Chrome doesn't have this warning at all, hence it not showing up there.
Sadly, it's the only clue I have as to why my form's submit button isn't working.
The chance that this warning has anything to do with the submit button not working is low, unless it doesn't work in all browsers.