Credential Management: use InvalidStateError for non-fully active docs
Categories
(Core :: DOM: Credential Management, defect)
Tracking
()
People
(Reporter: marcos, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Safari/605.1.15
Steps to reproduce:
Credential Management spec proposes to use InvalidStateError for when methods are called on non-fully active document:
https://github.com/w3c/webappsec-credential-management/pull/245
Comment 1•6 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Credential Management' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.
How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.
When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:
The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:
Describe any areas of concern to which you want the accessibility team to give special attention:
Hi Karen, this is just a potential bug fix based on a small spec change.
I've need info'ed Benjamin VanderSloot as I think he maintains the Cred Man implementation.
Comment 4•6 months ago
|
||
ACK. I'll look into this.
Comment 5•6 months ago
|
||
It seems that the a11y-review
was requested by a mistake, thus I'm removing the flag.
If there is, in fact, something that Firefox Accessibility team could provide an engineering feedback on, please re-submit the request but with the information required in the template. More information is in the Accessibility review documentation
Comment 6•5 months ago
|
||
The severity field is not set for this bug.
:bvandersloot, could you have a look please?
For more information, please visit BugBot documentation.
Updated•5 months ago
|
Description
•