argoproj / argoproj/argo-workflows
Implement a browser support policy
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Implement a browser support policy for the UI
# Use Cases
When contributing to the UI, it would be useful to know what our browser support policy is to determine what browsers we should be testing against and what features are available to us (and potentially, when we can use new features).
In past projects, I've had a simple support policy to start out with:
* Chrome (Latest, Latest - 1)
* Firefox (Latest, Latest - 1)
* Edge (Latest, Latest - 1)
* Safari (Latest, Latest - 1)
We could start there see what demand looks like for older versions or different browsers. We should also consider the extent to which we want to support Mobile/Tablets and decide on a support policy there as well.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the UI contribution and browser-testing guidance, then resolve the supported desktop and mobile/tablet browser matrix. Done means the policy is documented clearly enough to guide testing and feature choices.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100