5,017 karma · joined December 8, 2015
For Go, I don't know any (but might be wrong, googling did not turn up anything).
Happens for the map at Google Flights (https://www.google.de/flights/) that is the No 1 search result when googling for Flights (that's of course a clever move by Google to create a top site that only works fine with Chrome, I wonder how long it will take that YouTube or GMail only work "optimal" with Chrome)
Anyway, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1329141 but this is only P3 priority (that is, marked a "valid" bug but nobody is working on it). Which I found really "strange" because website not working in Firefox and being force to temporally switching to Chrome (and maybe staying) are the worst that can happen. Eventually, when booking a flight I even had to tell other family members that they should use Chrome for it (who were surprised because normally I tell them to use Firefox ;)
Discussion of the Firefox approach: https://news.ycombinator.com/item?id=13493407
In my experience: You should "refresh" your Firefox, see https://news.ycombinator.com/item?id=13227658 It help in my case.
Mostly, because preinstalled with Windows and then installing yourself is still cheaper than buying from a small, single trader.
Also a bit of Orwell's Newspeak in here as well. In the end it's funny of course :)
You mean JS code in the debugger? You may want to raise an issue for this in the new debugger which seems much faster developement progress: https://github.com/devtools-html/debugger.html
Or html in Inspector or CSS in the rule view?
Give it a try: https://developer.mozilla.org/en-US/docs/Tools/Migrating_fro... and https://developer.mozilla.org/en-US/docs/Tools
See your sibling below: > Unsigned addons cannot be enabled on beta or release. That was only available for a limited time. Now they can only be enabled on alpha (aka developer), nightly, or special unbranded builds.
Backup/Restore your bookmarks etc. afterwards as it cleans up everything. Resetting everything afterwards took 1h for me but was totally worth it in retrospective.
Overall, I like the (dark) theme UI/UX better, and also the DOM node hightlighting better.
The eyedropper and the full page screenshot tool are great too (do not know if Chrome also has it). And using all these tools from the devtools command line: https://developer.mozilla.org/en/docs/Tools/GCLI
There are drawbacks like the new debugger which is missing a lot common tiny usability features currently (making it hard to use) - and it's still buggy. But it's rewritten from scratch using modern technologies like react/webpack. So it's evolving fast.
Edit: Fixed typos.
You might want to leave a comment on how/why (use case) you used it to help to priorize the bug.
There's a Firebug Gaps meta bug which depends on this: https://bugzilla.mozilla.org/show_bug.cgi?id=991806
Unfortunately, tilt (or 3D View) does not work with e10s (multiprocess) enabled. There's a bugreport/issue somewhere at bugzilla:
AFAIK the firefox devtools team has plans/ideas that the devtools could just used like a normal Web App (loaded from a server). Currently, they are migrating XUL based components over to normal html what would make this possible.
As an example, just like debugger.html which can even be used from any browser in a not-builtin way: https://github.com/devtools-html/debugger.html