The most recent data loss incident was when I was trying to use the New York DMV website to upgrade to a RealID driver's license at the same time that I was changing my address. Validation error on one page became unrecoverable (fixing the problem didn't fix it) and going back started me at ground zero.
I then tried the same flow on Chrome (including the validation error) and couldn't get it to repro; things just worked. Totally possible that the actual failure was unrelated to the browser -- I never tried to establish a consistent reproduction on Firefox.
The other one was using SAP Concur for an expense report in a corporate environment. This is a horrible experience regardless of browser, but I ended up closing out Firefox and finishing the report in Chrome because things kept giving me strange errors.
This is such a great example of the problem with Chrome dominance.
You've come to believe that Firefox is broken with respect to Chrome. When in reality you only know that websites work better in Chrome. But that's not because Chrome works better, it's because those web teams only test against Chrome, and when Chrome is broken, they break their own website to match, so it works in Chrome but not other browsers.
This is exactly the danger being highlighted in this thread. How long until the DMV site and Concur (and other sites) have little notes that say "Chrome required to use this website"? And then we're right back to the bad old IE days again.
I then tried the same flow on Chrome (including the validation error) and couldn't get it to repro; things just worked. Totally possible that the actual failure was unrelated to the browser -- I never tried to establish a consistent reproduction on Firefox.
The other one was using SAP Concur for an expense report in a corporate environment. This is a horrible experience regardless of browser, but I ended up closing out Firefox and finishing the report in Chrome because things kept giving me strange errors.