Need general policy for which browsers to support in which contexts

[cfarm]

Make it clear which browsers, functionality to test, and how.

Tasks

draft a policy/recommendation from FEWD perspective

For an upcoming meeting (12/5):

• Cat will create a Google Doc
• Share out to get questions/suggestions from FEWDs in advance.
• During meeting, we'll start live-drafting the policy together!
• Go line by line through current list of support and discuss and make decisions on changes.

once FEWDs approve draft

• present it to stakeholders (designers, product owners, Adam)
• adjust with feedback as needed
• get signoff on making this the standard

Acceptance criteria

• Make sure you have an experience that’s as feature complete/accessible as possible for each browser in list.
• Do we want to specify CSS/HTML features too? Especially what fallbacks are needed or polyfills - with and without js
• What level of support are we committing to from now on?
• With what methods will we test and achieve that support?(For example, we may decide to manually test some browsers until automated testing is implemented, etc).

[cfarm]

we labeled this HH meaning "double high priority" 😸

[contolini]

• How do we talk to stakeholders about the importance of browser support?
• If you feel you can’t support our baseline browsers given complex project requirements, what should you do?
• If your think your project has a unique user demographic with unusual device usage, how can you safely stray from our standard browser support guidelines?

[cfarm]

More wishlist for outcomes for this task

• Understand when we can adopt the newest browser features
• Standardize our decision-making process
• Feature-based descriptions of support such as specific DOM events or component/UI interactions

[cfarm]

@jimmynotjim and @virginiacc volunteered to draft a proposal to define an active vs passive browser support policy based on Virginia's idea

[cfarm]

@Scotchester volunteered to do the following task for this:

Sketch potential application of active/passive support policy. It should help us answer the question, “How would we apply the policy to pages/browsers?”

[cfarm]

@Scotchester please share an update when you're back!