ratman150@sh.itjust.works to Firefox@lemmy.ml · 5 months agoHow about no?sh.itjust.worksimagemessage-square141fedilinkarrow-up11.4Karrow-down119file-text
arrow-up11.38Karrow-down1imageHow about no?sh.itjust.worksratman150@sh.itjust.works to Firefox@lemmy.ml · 5 months agomessage-square141fedilinkfile-text
minus-square4am@lemm.eelinkfedilinkarrow-up34·5 months agoYeah seriously, what is so special about what they’re doing here that it has a browser-specific bug? This isn’t like 20 years ago where browsers had tons of experimental and custom extensions to HTML and JavaScript in them. It’s all standard now.
minus-squareBlue_Morpho@lemmy.worldlinkfedilinkarrow-up13·edit-25 months ago It’s all standard now. The reason Microsoft surrendered to Google and adopted Chromium is they couldn’t keep up with Google’s changes to standards and proprietary extensions.
minus-squareBransons404@lemmy.worldlinkfedilinkarrow-up4·5 months agoThere are still several css differences between chrome, ff and safari. It’s a pain to develop for them, but it is possible
Yeah seriously, what is so special about what they’re doing here that it has a browser-specific bug?
This isn’t like 20 years ago where browsers had tons of experimental and custom extensions to HTML and JavaScript in them. It’s all standard now.
The reason Microsoft surrendered to Google and adopted Chromium is they couldn’t keep up with Google’s changes to standards and proprietary extensions.
There are still several css differences between chrome, ff and safari. It’s a pain to develop for them, but it is possible