* fix item 2: All page content should be contained by landmarks
* fix item 4. Elements must only use permitted ARIA attributes
* fix item 6. ARIA attributes must conform to valid values
* fix bug on item 6. and fix item 7. <ul> and <ol> must only directly contain <li>, <script> or <template> elements
* fix item 8. Interactive controls must not be nested
* fix item 10. ARIA toggle fields must have an accessible name
* fix item 11. autocomplete attribute must be used correctly
* fix item 12. Form elements must have labels
* fix item 14. ARIA input fields must have an accessible name
* fix item 15. Buttons must have discernible text
* fix item 16. Images must have alternative text
* working on item 17
* finish fix item 17. ARIA role should be appropriate for the element
* fix wrong role in hidden inputs
* address pr comments
* Add auth provider config page for Amazon Cognito
* Fix e2e test
* Fix issue with cross-origin and the popup
* Change name on login screen and reduce code change
* Fix lint
* Fix e2e tests - fix bugs in po change
* Update auth-config.js
* Remove rancher url from test
* Address PR feedback
* Use selection grid
* Use selection grid po correctly
* Address Phil's PR feedback
This prevents the default form submit behavior in `ldap.vue`.
#13954 introduced a change to resolve issues with focus behavior when the async button component entered a disabled state. It turns out that the disabled attributed on the button was preventing the default submit behavior, and changing this reintroduced the default form submit behavior.
The recommended way to submit forms in vue is to utilize `@submit.prevent` to disable the default form submit behavior and define our own submit logic. We want to retain the changes made to async button so that keyboard focus remains consistent.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
* add role 'none' to hr elements in TopLevelMenu
* add missing role and label to SideNav
* add aria-label to show/hide button in the Password component
* add role 'none' to hr elements
* add missing alt to user avatar image
* Add comment about the logic behind the goToClone methods
* Remove verbs key manipulation and map verbs with methods
* Add tests to ensure verbs are not manipulated
* Fix linters
- Remove custom code, use new generic code that follows 'compact' concept
- Apply to all four fields in row
- Also fix a bug where selected verbs such that another row is shown would grow height of other inputs
Fix height of Create Project Resource Quotes input fields
- Vue2
- Component would inherit attributes, such as class from owning element. For example classes applied to `<Select` would be applied to the first element within the Select component
- $attrs property does not contain some properties from the parent, such as class
- Vue3
- Component does not inherit attributes of owning element
- $attrs property contains all propertiesof parrent, including class
- Bug
- We fixed part one, but not part two
- in Select we were applying class twice, manually to parent and then automatically to v-select
- solution is to fix part two (chop out class)
Performing this change so the vue3 migration script can modify all @input, @v-model of components without changing plain elements. This will reduce the number of vue3 compiler errors.
* Add users and roles tests
* Refactor: split user-and-auth.po into user.po and roles.po and added roles tests
* Refactor users to reflect underlying list, create/edit and detail components
- Make Users PO root page for users list.
- contains list po which extends BaseResourceList
- contains user specific list stuff
- Move create edit stuff to own PO
- Move detail stuff to own PO, extend ResourceDetailPo
* Update roles as per previous changes to users
- different to users given different resource types
* split users and roles tests
* Remove unrequried command.ts, make http 200 check more lenient
---------
Co-authored-by: Yonas Berhe <yberhe@Yonass-MacBook-Pro.local>
Co-authored-by: Richard Cox <richard.cox@suse.com>
* fix issue with Resources Select in globalRoles edit/create interface
* address PR comments
* add missing check
* Minor improvement, add comments
- Did a deep dive on what this should actually be doing, added comments to explain
- We should prioritise methods to find a key via config before falling back on label and random string
- The opt.optionKey has been (previously) applied incorrectly. It should be the actual option key, rather than a key to find the option key
- This is the root of the issue.
- I don't think we should fix this here in case of breaking somewhere else
- The changes in the PR are one's we should be doing anyway
---------
Co-authored-by: Alexandre Alves <aalves@Alexandres-MBP.lan>
Co-authored-by: Richard Cox <richard.cox@suse.com>
* Auth Provider: Support Okta with LDAP search
* Minor fixes
* Update UX and add detail of LDAP configuration
* Fix issues when logging out
* Fix i18n key