201–206 of 206 posts
This appears to be a simple rebrand of Aurora with some extra features[1]. [1] - https://bugzilla.mozilla.org/show_bug.cgi?id=1076914
The linked bug's access rights are limited; Mozilla won't show it to me. Is that the right bug?
Earlier quoted context omitted.
That reminds me: It would be nice if you could open several different incognito windows, each with their own session. That way one can debug user interactions without needing as many browsers as users in the interaction (or half of it because each browser has it's own incognito session in addition to the normal session).
A workaround that I've used before is to connect to my site via the domain name in one tab, and the IP address in another - cross domain protection ensures I get two nicely partitioned sessions.
I wonder if they'll remove (or at least most of it) developer tools from the main browser and try to get developers to use this version. Common criticism of Firefox these days is it feels (and in most cases is) slower and more bloated than Chrome. This move could help Mozilla make FF faster, no?
Well, the main advantage that Chrome has vs Firefox is not speed (these days, Firefox is faster than Chrome on most benchmarks I have seen), but smoothness, which is largely due to the multi-process architecture of Chrome. Developer tools have strictly no influence on this, and the multi-process version of Firefox is currently being tested. I don't remember whether there is an ETA.
JavaScript speed is not what needs to be worked on currently. Render speed is.
Sounds cool. Shame that Mozilla's developer tools are in some respects that are important to me still inferior to Chrome.
How so? I'm asking because two Firefox devtools people sit in my office, so if you have feedback, I can forward it.
Earlier quoted context omitted.
Generally by asking them to paste code into the JavaScript console. Here's an example: http://sdpcfix.com/security-alerts/facebook-scam-helps-trick...
We should instead remove access to the keyboard, that would be a way more effective way to stop any situation where theses users would cause a security issue. Seriously, it's not the first kind of attack that appear because users are too naive. At one point we need to trace the line somewhere. Should we also block copy-paste to a file in case they create a batch file?
Earlier quoted context omitted.
We should instead remove access to the keyboard, that would be a way more effective way to stop any situation where theses users would cause a security issue. Seriously, it's not the first kind of attack that appear because users are too naive. At one point we need to trace the line somewhere. Should we also block copy-paste to a file in case they create a batch file?
Greasemonkey has similar protections around copy-pasting userscripts, for this very same reason. It's not so unreasonable