rauno

What's the status on this one? It doesn't seem like this has been resolved since there are no warnings on assigning symbols or functions to the `defaultValue` prop. Even found...

I checked earlier and I might be wrong but I'm quite sure this was fixed earlier by @nhunzaker ``` // Same goes for the `value` prop return ( {}} />...

Although, `textarea` seems to behave differently - not sure if intentionally or not. ``` function App() { return ( {}} /> {}} /> ); } ``` Both functions get stringified...

> This looks perfect now. Thank you very much 🙂 If you want a follow-up task, you could work on the same fix for elements. @philipp-spiess Do you mean working...

Input, textarea and select are now covered. I can't think of any other form elements where these attributes might be an issue. Should be all good.

@chancestrickland any additional thoughts on this? A nav skip link sounds like the natural choice for me, so I'd go with that!

@chancestrickland wdyt?

Yeah. I also feel like this increases the scope too much for the initial release. Also, this got me thinking if `axe-mode` should be specifically tied to the `axe` name,...

Interesting idea! I'm not sure if this would be worth it for a couple of reasons: 1. I feel like the overlays are superior to console warnings, which are just...

> Or better yet, perhaps, what if the component name linked directly to open up a tab in React Dev Tools if the user has it installed in their browser?...