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
Do you want to request a feature or report a bug?
A feature
What is the current behavior?
Since React 16 we have the ability to define any attribute and it is passed to the DOM (contrary to the whitelisting approach of earlier versions). An exception are all attributes starting with on - for obvious security reasons. (Source)
However, this restriction makes it impossible to write interactive AMP pages in React, since all actions are defined using the on attribute. (Example)
What is the expected behavior?
It should be possible to use the on attribute, so that it is also passed to the DOM.
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
All React Versions
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
A feature
What is the current behavior?
Since React 16 we have the ability to define any attribute and it is passed to the DOM (contrary to the whitelisting approach of earlier versions). An exception are all attributes starting with
on
- for obvious security reasons. (Source)However, this restriction makes it impossible to write interactive AMP pages in React, since all actions are defined using the
on
attribute. (Example)What is the expected behavior?
It should be possible to use the
on
attribute, so that it is also passed to the DOM.Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
All React Versions
The text was updated successfully, but these errors were encountered: