To use this directive, just import it to your module and add to Declarations section. Var elems = document.getElementsByName(this.prevElemName) If (elems & elems.length & elems.length > 0) Var elems = document.getElementsByName(this.nextElemName) * You should modify the above declarations as follows:
* to the first and last controls of the dialog. * Usage: add "custom-taborder" and "tab-next='next_control'"/"tab-prev='prev_control'" attributes As soon as the active AF point(s) have a clear view of the actual subject again, press the back button to re-engage focus upon it. * (when tab key allows to move focus outside of dialog). With back-button AF, if you sense the camera may try to focus on an unwanted foreground object, just lift your thumb off the back button for a moment freezing focus temporarily and keep following the subject. * Particularly useful for working around the modal dialog TAB issue NonModalNodes = document.querySelectorAll('body *:not(dialog):not()') įor (var i = 0 i < nonModalNodes.length i++) from This directive allows to override default tab order for page controls. corrupt the previous state of the element if a modal was already open by only finding elements that do not have tabindex="-1" we ensure we don't Var modalNodes = om( document.querySelectorAll('dialog *') ) If you're creating a generic dialog library, the only thing I have found that works reasonably well is to either use the inert polyfill or make everything outside of the modal have a tabindex=-1. If you always control all the elements within the dialog (and you're not creating a generic dialog library), then probably the easiest way to go is to add an event listener for keydown on the first and last focusable elements, check if tab or shift tab was used, and then focus the first or last element to trap focus. However, with the rise of web components and shadow DOM, this solution can no longer find all focusable elements. One solution that is popular is to create a query selector of all known focusable elements and then trap focus to the modal by adding a keydown event to the last and first elements in the modal. I'm not sure the status of the proposal, but it doesn't look like it will be implemented any time soon. However, adoption has been slow and only recently did it land in Chrome Canary behind a flag.Īnother proposed solution is making a native API that would keep track of the modal stack, essentially making everything not currently the top of the stack inert. The inert attribute was proposed to try to solve this problem by making any element with the attribute and all of it's children inaccessible. There is currently no easy way to achieve this.
0 kommentar(er)
