On Thursday, 7 August 2014, Jesse Glick <jgl...@cloudbees.com> wrote:
> It would be best to try to degrade gracefully on older or less > functional browsers. If the page looks ugly, fine. If some JavaScript > tricks do not work, fine, so long as there is some other way to > accomplish the same task. I think what we are after is 3 tiers: - first class UX (we should aim to proactively fix these browsers and provide an equal UX across all) - UI testing failures here are considered major UI bugs - best effort UX (we will accept patches to fix issues and attempt to ensure there is at least one way to do any action with these browsers) - UI testing failures here are only considered major bugs if they completely block functionality, if the UX degrades but remains functional or if there is another way to do it, then it's a minor bug - no guarantees - no UI testing - UI bugs closed as will not fix So IE 11 should be first class, say IE 8 or 9 is best effort and IE 7 and below is no guarantees > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com <javascript:;>. > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
