Page Comparison

Browser Support

Discussion Notes:

• Define "support"
  • FOLIO runs pretty well on most major browsers. Generally when find out, fix if we can. They don't always make it to the team that can fix them. Dev teams sometimes reject the bug when Zak or John could have been patched.
  • Instead say only test in Chrome but generally expect it runs in most modern browsers. Perhaps this would allay concerns.
• How can we route the bugs to a team that is better able to triage them. Would need to set expectations around that. Not every browser bug could be fixed.
• Are hosts willing to provide some user agent data?
• Balancing bugs vs feature attention priorities
• A more holistic view of support
• Craig: will see if FSE can send UA stats
• Talk to support SIG?
• Interactions WRT tablets
• Can offer definitions of major/commonly used browsers
  • Collect stats first
• Way to set clear expectations and get everyone on the same page
• Security implications?
  • Browser specific issues?
• Accessibility implications?
  • Will test on browser with specific version
  • Know it works where tested it
  • Policy about where else to test it
  • A lot of work gone into a good automated testing framework, human review would require more resources. Accessibility SIG?