Breaks pure-render checks

Open necolas opened this issue 10 years ago • 3 comments

This module generates new a11y id's every render, meaning that pure render mixin doesn't work.

Jun 27 '15 20:06 necolas

Why is this important for testing accessibility?

Sep 01 '15 07:09 blairanderson

It's an issue because during development performance of the application is extremely poor with react-a11y enabled. Ideally we'd like to keep react-a11y enabled always so that new warnings are immediately visible to developers.

Sep 01 '15 15:09 EvHaus

Yeah it's important because it slows iteration speed in development and makes it hard to identify similar performance regressions not caused by react-a11y.

Sep 01 '15 17:09 necolas