3 ms·
For anyone who works at the company who does that: why you do it? Is it to reduce amount of testing, and only have a few "blessed" browsers with guaranteed hap
by jakub_g 5y ago
For anyone who works at the company who does that: why you do it?
Is it to reduce amount of testing, and only have a few "blessed" browsers with guaranteed happy experience? Any other reasons?
- op00to 5y agoIt’s not so much for happy experiences, as it is to place bounds on what the development team is asked to do.
- graindcafe 5y agoThey may have spotted a bot using this UA and deduces it's a pattern
- tootie 5y agoI mean there's an excellent and obvious answer and that's cost benefit when it comes to QA. Anything transactional, banks in particular, want to be 100% sure that end user experiences are doing exactly what they're expected to at all times. No one is being served incorrect information or is improperly served terms or disclaimers that they can use a leverage in a lawsuit. The tech teams likely have an explicit support matrix of browsers to test against and anything not on the list is considered untested and unreliable. They can't legally indemnify themselves against defects.
- jakub_g 5y agoInteresting point on lawsuits! I never thought this way (maybe because lawsuits sounds like a very American thing, and I'm in EU)