Feature Request(?): Ability to run the browser support tests explicitly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
Hey there! 👋
I was wondering if it was possible to expose a way to run the browser support tests explicitly. I have things that trigger off the change of focus and ran down a bug today that was happening because of the browser support tests changing the focus.
I'd love some way to manually and explicitly run the support suite so it can build the localStorage item, and anywhere we use Ally functions they can use that cached version.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the browser support tests and the Ally functions that use the cached localStorage result. Determine how an explicit support-suite entry point should build that item without unexpectedly changing focus, then verify the focus-triggering behavior and cached result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100