[SVG] Support "focusable" attribute
See original GitHub issueCurrently, if I supply a focusable
attribute to the SVG, it shrinks it out. Seems it happens because there is no focusable
key in SVGDOMPropertyConfig.js.
So is there any chance you merge a PR which adds this property to the list?
Issue Analytics
- State:
- Created 8 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
Managing focus in SVG - ally.js
The focusable attribute defined by SVG Tiny 1.2 is only implemented in Internet Explorer and Microsoft Edge. Unlike tabindex this attribute has a...
Read more >Require <svg> to have focusable attribute (svg-focusable)
Inline SVG elements in IE are focusable by default which may cause issues with tab-ordering. For instance, if a link or button has...
Read more >SVG focusable attribute is not working - Stack Overflow
I used focusable attribute to force SVG elements get focus in HTML document. I need to navigate in SVG elements in SVG tag...
Read more >tabindex - SVG: Scalable Vector Graphics - MDN Web Docs
The tabindex attribute allows you to control whether an element is focusable and to define the relative order of the element for the...
Read more >Interactivity – SVG Tiny 1.2 - W3C
13.12.1 The 'focusable' attribute. In many cases, such as text editing, the user is required to place focus on a particular element ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
IE10, IE11, and Edge support
focusable
, unfortunately. If you don’t specifyfocusable="false"
, SVG elements are added to the tab order by default in those browsers, with no way of removing them (tabindex
is ignored).It’s a pretty annoying accessibility issue for keyboard users in those browsers.
Moved to https://github.com/facebook/react/issues/12481.