FWIW, I've written any new JS/HTML/CSS according to caniuse.com and their base line supported level, though that might be fairly conservative (not as conservative as the current Jenkins wiki, though!)
On Fri, Nov 15, 2019 at 8:15 AM Daniel Beck <db...@cloudbees.com> wrote: > I think Firefox ESR would make sense to support as well. Its baseline is > never older than a year IIUC, so should be feasible to have it be > considered supported. > > Showing warnings on the UI when using an unsupported browser would > probably be fairly straightforward as well, and help to inform users. > Perhaps we even distinguish between "outdated based on policy" and > "outdated based on features actually used in core or popular plugins", but > that may end up being too much effort to maintain. > > > Does it actually make sense to still support IE? > > On Fri, Nov 15, 2019 at 10:17 AM Oleg Nenashev <o.v.nenas...@gmail.com> > wrote: > >> Hi all, >> >> There was recently a question about Jenkins browser support policy raised >> in the chats. Currently the policy is hosted on Wiki (here >> <https://wiki.jenkins.io/display/JENKINS/Browser+Compatibility+Matrix>), >> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully >> supported, ouch. It does not look like we had any major changes since the >> inception of the policy in 2014. I have created a pull reques >> <https://github.com/jenkins-infra/jenkins.io/pull/2649>t to move the >> policy to jenkins.io, and I would like to make some changes to actualize >> it. >> >> What do I propose? >> >> - Chrome, Firefox, IE, Safari >> - Level 1: >> - "Latest regular release, latest minor release / patch level" >> - Level 2: >> - Previous patches of the latest regular release >> - Latest minor release / patch level for the "Version -1" >> - Level 3: >> - All other versions >> - Other browsers, including mobile versions, Chromium, Microsoft >> EDGE, etc.: >> - Level 2: Latest regular release, latest minor release / patch >> level >> - Level 3: All other versions >> >> >> This policy should be somewhat aligned with the current ATH state. IIUC >> we test only Firefox now, and there is a PR by Oliver Gondza to run tests >> on Chrome instead (here >> <https://github.com/jenkinsci/acceptance-test-harness/pulls>) >> >> WDYT? >> >> Best regards, >> Oleg >> >> -- >> 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. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > > Daniel Beck > Senior Software Engineer > CloudBees, Inc. > > [image: CloudBees-Logo.png] > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Matt Sicker Senior Software Engineer, CloudBees -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oyaa7gXJpdQ1aFh6Kd89cDQ8MMQJWDxhkmLdpkjH5J_Ew%40mail.gmail.com.
