2 ms·
In most of my jobs, as soon as Firefox presented any kind of issue or inconsistency, support for it was dropped. In my first job, we had an inconsistency in how
by MattGaiser 4y ago
In most of my jobs, as soon as Firefox presented any kind of issue or inconsistency, support for it was dropped. In my first job, we had an inconsistency in how Firefox handled datalist vs how Chrome did. Firefox support officially ended at standup the next day.
That being said, I do have a (largely dormant) MBNA account if anyone has specific checks they want to do.
- torstenvl 4y ago> That being said, I do have a (largely dormant) MBNA account if anyone has specific checks they want to do. You mean... if anyone has specific checks they want to have you do? Not my practice area, but letting someone circumvent anti-terrorism banking laws seems like something you'd definitely want to seek legal advice about before acting.
- postalrat 4y agoDropping support the day after you find an issue just means it wasn't supported. Pretty bad signal for anyone depending on your support.
- MattGaiser 4y agoIn that case we only had major municipal users and I only remember one being impacted, so it was easy enough to tell them to ditch Firefox for Chrome.
- postalrat 4y agoMaybe stop telling them you support chrome and instead tell them chrome works with your site.
- vlod 4y agoI web develop first using Firefox and I can't ever remember a time that it failed to run on chrome. Not sure if you remember the "good old days" when people coded only for IE (because what's the point... the rest be damned). We had EXACTLY this same attitude. MSFT then let IE6 stagnate. Most likely we won't have the same fallout with chrome (as there are quite a few derivatives), but do we really want to just have one code base? (chromium). Having competition is good. We should do whatever we can to stop Firefox dying, IMHO.
- deleted 4y ago[deleted]