4 ms·
Sometimes that's not an option. We were once forced to do the same thing. Block Opera, that is. We had a large-ish JS app which ran fine in FF and IE, but gene
by nimbix 17y ago
Sometimes that's not an option. We were once forced to do the same thing. Block Opera, that is.
We had a large-ish JS app which ran fine in FF and IE, but generated all sorts of exceptions in Opera. The reason we didn't fix it was that every single one of those errors read something like "There was an error in [function].". No line numbers, no surrounding code, no nothing. So we blocked it.
(We did eventually fix the bugs, but only after a new version of Opera which printed more informative messages was released.)
- ars 17y agoSo why block them? Why not a message: "This site probably doesn't work in Opera, but feel free to try."?
- nimbix 17y agoBecause sometimes it wasn't immediately obvious that something was broken without looking at the error console. This was a business app and if, for example, a form widget failed to work properly it could result in silent data loss which wouldn't get noticed for a while.
- trevelyan 17y agoBecause the customer's perception of your professionalism matters, and the problems with the browser's execution of javascript would strongly and negatively affect their likelihood to use your service and convert to a paying customer? My site depends heavily on custom-coded javascript. Minor browser inconsistencies are one thing you expect to handle or live through. Absolute FAIL because of poor javascript engine implementation is another.