0

Wanted for once use FireFox for dev / tooling.

Welp, it only took 1 page load to see why devs don't use it :

There is NO information on how long an ajax request took.

A lot of useless stuf like "Destination IP" (Who the fuck cares?) or "Initiator" (I already know where it started, I want to iknow how long it took).

That concludes my try to work with a non chromium browser and i'm sad. because chromium is a new IE6.

Don't belive me ? Look how websites manages checkboxes. Yes that's right with ::before and ::after.

These pseudo elements SHOULD NOT work in <input>. But they do in chromium. Which basicly a deal break to use firefox for our users.

Fuck you chromium. IE6 bis i'm gonna call you now

And FireFox : Please, just COPY dev tools of chromium, yours are unusable.

Ok, I feel better, going back to my bug.

Comments
  • 0
    Edit : keeping original rant, but I found the option I needed, it was hidden in a sub menu for "reasons" I guess.
  • 0
    I personally hate firefox as a Dev. It keeps crashing, the debugger eats more ram than every instance of chrome that ever existed and many things break in Firefox JS for unknown reasons. I can write you 10 lines of JS that behave completly different in Firefox than Chrome.
    And now with fucking Edge taking over Firefox in marketshare you know it's a sinking ship.
Add Comment