Jaden Norman@lemmy.world to Technology@lemmy.worldEnglish · 1 day agoFirefox is fine. The people running it are notwww.theregister.comexternal-linkmessage-square138fedilinkarrow-up1678arrow-down112cross-posted to: technology@beehaw.org
arrow-up1666arrow-down1external-linkFirefox is fine. The people running it are notwww.theregister.comJaden Norman@lemmy.world to Technology@lemmy.worldEnglish · 1 day agomessage-square138fedilinkcross-posted to: technology@beehaw.org
minus-squareMinusPi (she/they)@pawb.sociallinkfedilinkEnglisharrow-up17arrow-down1·5 hours agoIt’s so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you’re already doing something very, very wrong.
minus-squarebuddascrayon@lemmy.worldlinkfedilinkEnglisharrow-up2·2 hours agoChromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.
minus-squaresheogorath@lemmy.worldlinkfedilinkEnglisharrow-up8·4 hours agoYep, this is why at least for me when I develop websites I use Firefox first for development to make sure that the website runs on Firefox.
minus-squareokmko@lemmy.worldlinkfedilinkEnglisharrow-up1·edit-24 hours agoThis is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
minus-squareM0oP0o@mander.xyzlinkfedilinkEnglisharrow-up4arrow-down1·4 hours agoThe how is testing on one other browser.
It’s so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you’re already doing something very, very wrong.
Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.
Yep, this is why at least for me when I develop websites I use Firefox first for development to make sure that the website runs on Firefox.
This is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
The how is testing on one other browser.
What a novel idea.