Gregory's Serverif your web app doesn't work in firefox your web app doesn't work. it's literally broken. fix it.
|
josh :bocchi_arch:
36 comments
Kevin Karhan :verified:
@josh What really gets me to going ballistic is #AdblockerBlockers, forced-in & technically unnecessary Cookies and noreply- eMail- and Vanity Numbers: All that shit should be so very illegal that I think @Netzausbau sould terminate any NoReply - Line or domain using such eMail Adresses.... 
redvers
@ellenor2000 @geerlingguy @josh lynx is used for accessibility reasons, text to speech, text to braille. If your web app is something a blind person might want to use, why not make it accessible to them? 
Bjornsdottirs
@redvers @geerlingguy @josh ?????? no it's actually a very primitive text-mode web browser that as far as I know isn't very screen-reader accessible (as most UNIX terminal apps aren't).
Bjornsdottirs
@redvers @geerlingguy @josh that was the weirdest interaction I've ever had, I'm gonna go drink the strongest coffee I've had
Allen B. Skye
@josh Back in the olden days (early 2000s) when my buddies and I ran a fun little website where we reviewed cheesy horror movies that had 10s of visitors, I checked our simple html/css website with Internet Explorer, Opera, etc just to make sure it functioned the same in all browsers. Granted, it was a different scale & function but still... 
Braw :blob_cat_melt: π³βπ
@josh you can say that when Firefox implements all APIs other browsers have, things like PWAs, but while it's slower to get features than Safari, no, lol, if your app isn't working in Firefox, Firefox messed up
Gaveen Prabhasara
@lscottspencer @brawaru @josh I hope these facts serve you well when the ad company decimates the web severely enough to the point where it only works in the ad company's browser... with ads. πβπΎ
DELETED
@gaveen You're more than welcome to your opinion. You aren't allowed to make unfounded claims without reasonable rebuttal. Use what works best for you. But, don't declare one product superior to another. You prefer Firefox. That's great. But, the feedback you received was more than fair. @brawaru @josh
Gaveen Prabhasara
@lscottspencer @brawaru @josh Likewise. I made no point about superiority of anything nor made any unfounded claims. If anything, I was pointing at the pitfall of embracing Chrome/Chromium monoculture (due to whatever technical merit) in light of the systematic dismantling of ad-blocking and the muscling through of preferred tech adoption that one company (who owns a big ad network) is doing. It'll be a sad day when pointing this out only warrants righteous ire. But we're not there yet.
DELETED
@gaveen These things move in cycles. Internet Explorer did the same thing and led for years. Firefox emerged as a solid competitor for awhile. Apple worked with Google until they didn't. Chrome is leading now and will fall out of favor when something better comes along. Firefox did themselves in with the decisions they made and the bad leadership they had. Use what you like. That's the beauty of choice. I like PWAs. Full support for them is near the top of my list. @brawaru @josh 
billy joe bowers is tired.πΊπ¦
If your website or app doesn't work with Firefox then I won't see it. I sometimes use Safari as a backup, but for that I won't even bother. Not interested.
MaybeMyMonkeys
@josh testing against Firefox will probably find issues that are missed by Safari and Chrome
Reid :blobcat3c:
@josh@phocks.eu.org it's already broken by being web, the web itself is broken at the very core and should jist be set on fire so we can start over with something sane
ADisorderlyFashion
@josh If 1 in every 20 people who might theoretically use your webapp is metaphorically given the finger for using the wrong browser, your webapp doesn't work. 
chidi_anagonye
It is really quite simple. KISS. Focus on function and usability, not aesthetics. It should function without JS. JS should be for niceties. That is all. 
Rep Rap Ryn :3
@josh and we go right back to folks only developing websites for IE6, like we never learned a thing. 
Andrew Douglass
@josh the web app Iβm building depends on low level APIs that Firefox says are too dangerous to users to implement, like WebUSB. Apparently prompting the user for permission to access a physical device isnβt good enough. Is my app broken or is Firefox the problem in this case?
Stuart Celarier
@josh Perhaps the app isn't the problem, the browser is? With less than 3% market share globally, Firefox has been behind implementing standards, and lacks features like support for PWAs, making it difficult and expensive to include in a software development project. In business web app development, I think it has been many years I have seen a project that included Firefox in the list of targeted browsers. Unvarnished economics. Not that using it is wrong, it just comes with certain realities. |
@josh +9001%
Same goes with any other standard-compliant browser:
If a #website is not fully useable in #LynxBrowser it's ableist and not #accessible and needs to be fixed!