You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which exact UI Library version are you using? For example: 1.0.1 - don't just write v1.
1.5.0
Bug summary
In Umbraco V13, we had to disable the Shadow DOM for the time being in the uui-input component to make autofill and password managers work in Chromium browsers. However, this throws a warning that a duplicate #input ID is detected (one for each time you show the component on the page).
The question is if we can first of all make sure the uui-input can run without a ShadowDOM, and second of all avoid using ID's in the inner template (or allow a custom ID) just in case.
This can be avoided locally by overwriting the getFormElement method as well as removing the id on firstUpdated, but ideally it would be possible to change the id:
import{UUIInputElement}from'@umbraco-ui/uui';import{customElement}from'lit/decorators.js';
@customElement('umb-login-input')exportclassUmbLoginInputElementextendsUUIInputElement{protectedfirstUpdated(){constinnerInput=this.querySelector('input')innerInput?.removeAttribute('id');}protectedgetFormElement(): HTMLElement{constformElement=this.querySelector('input');if(!formElement){thrownewError('Form element not found');}returnformElement;}protectedcreateRenderRoot(){returnthis;}staticstyles=[...UUIInputElement.styles];}
Which exact UI Library version are you using? For example: 1.0.1 - don't just write v1.
1.5.0
Bug summary
In Umbraco V13, we had to disable the Shadow DOM for the time being in the uui-input component to make autofill and password managers work in Chromium browsers. However, this throws a warning that a duplicate
#input
ID is detected (one for each time you show the component on the page).The question is if we can first of all make sure the uui-input can run without a ShadowDOM, and second of all avoid using ID's in the inner template (or allow a custom ID) just in case.
This issue is seen on the new login screen of Umbraco 13: umbraco/Umbraco-CMS#15089
Specifics
No response
Steps to reproduce
This scenario can be replicated by extending
UUIInputElement
:Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: