GDSC-VU CORE TEAM LEAD FLUTTER DEV | Open-Source Contributor | Software Engineer | A Programmer With The Knowledge Of Technologies, Design, And Development Related To Mobile Applications.
If 'something wrong' means that it's Firefox - then this really is very poor work from Google. I've tried it on Firefox on three different OS - doesn't work. Making a website that doesn't work on all modern browsers is pretty much inexcusable.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
They could well support just Chrome and give a shit about the rest. Supporting Safari (the shittiest of modern browsers, the new IE) has probably been a great job, justified by the ~18% market share.
Maybe supporting a browser that has a worldwide usage around 3% like Firefox simply doesn't worth the time and I agree on that. It itches you because you're a FF user (extrapolated from the comments) but then there's Edge (with a bit more usage than FF btw), Opera, Samsung Internet, UC and many more.
I still think that if we Devs pick the browser with better support to new features (Chrome) and ignore the rest, the industry itself will be forcing lazy ass vendors either to upgrade their browsers or letting them die.
Because if we ignored the modern features back those days we would still create frontends like 10 years ago and the middle point where we live in is to add browser agent checks inside the code to see if something can be done or not (more work to everyone cause few didn't do theirs).
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
But all of them implementing features support on a reasonable time span would be a ridiculously good thing.
We are the clients of the browsers, doesn't almost the entire world -except for monopolies and oligarchies- work hard everyday yo stay up to date with new features by market pressure so we can keep current clients and maybe get more by innovation?
Well, seems that someone didn't do that kind of homework in some browsers.
Firefox Desktop doesn't even support PWAs, neither Safari (any version) brings a good support into it, that's hilarious in 2022.
Sadly some got advantage by being the default browser in some OS and then we need to deal with Safari instead ignoring it like we do with Firefox 🙃
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
I was referring to the Google interview thing the article is about.
I really have no idea why Firefox stopped work on PWAs for desktop (they support them on mobile) - for years it was possible behind a commandline switch (which has now been removed). It's totally capable of doing it - there are various workarounds/addons in place to do something close to it if you are so inclined... but looking at the actual issues in the bug tracker about PWA support it still seems very much on the back burner for now. Odd decision
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not pathetic. Maybe something wrong with your browser.
If 'something wrong' means that it's Firefox - then this really is very poor work from Google. I've tried it on Firefox on three different OS - doesn't work. Making a website that doesn't work on all modern browsers is pretty much inexcusable.
They could well support just Chrome and give a shit about the rest. Supporting Safari (the shittiest of modern browsers, the new IE) has probably been a great job, justified by the ~18% market share.
Maybe supporting a browser that has a worldwide usage around 3% like Firefox simply doesn't worth the time and I agree on that. It itches you because you're a FF user (extrapolated from the comments) but then there's Edge (with a bit more usage than FF btw), Opera, Samsung Internet, UC and many more.
I still think that if we Devs pick the browser with better support to new features (Chrome) and ignore the rest, the industry itself will be forcing lazy ass vendors either to upgrade their browsers or letting them die.
Because if we ignored the modern features back those days we would still create frontends like 10 years ago and the middle point where we live in is to add browser agent checks inside the code to see if something can be done or not (more work to everyone cause few didn't do theirs).
A browser monoculture is a ridiculously bad idea
But all of them implementing features support on a reasonable time span would be a ridiculously good thing.
We are the clients of the browsers, doesn't almost the entire world -except for monopolies and oligarchies- work hard everyday yo stay up to date with new features by market pressure so we can keep current clients and maybe get more by innovation?
Well, seems that someone didn't do that kind of homework in some browsers.
Firefox Desktop doesn't even support PWAs, neither Safari (any version) brings a good support into it, that's hilarious in 2022.
Sadly some got advantage by being the default browser in some OS and then we need to deal with Safari instead ignoring it like we do with Firefox 🙃
The most ridiculous thing is that if I swap the
user-agentto Chrome - it works 100%, no problems whatsoever. Shoddy work, or deliberate exclusion?LoL never tried it 😂 you mean in FF or Safari? And you tested the PWA thingy or that new Google webapp?
I was referring to the Google interview thing the article is about.
I really have no idea why Firefox stopped work on PWAs for desktop (they support them on mobile) - for years it was possible behind a commandline switch (which has now been removed). It's totally capable of doing it - there are various workarounds/addons in place to do something close to it if you are so inclined... but looking at the actual issues in the bug tracker about PWA support it still seems very much on the back burner for now. Odd decision