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
The one general comment I would have is that it feels that it is making the spec more complicated for hypothetical forwards compatibility. As discussed in meetings, an alternative could be to make it clear that nested divs are not allowed and if needed in a future version, that version will not be backwards compatible.
I know nested divs is not currently listed as a feature per se but if we continue with that approach into CR, I would like to mark it at risk to allow potentially removing it based on implementation feedback.
Closes#237 .
* Adds permitted feature `#scriptEventGrouping`
* Add at-risk features `#scriptEventGrouping` and `#scriptEventMapping`
* Adds link to at-risk feature logged in #239.
The one general comment I would have is that it feels that it is making the spec more complicated for hypothetical forwards compatibility. As discussed in meetings, an alternative could be to make it clear that nested
div
s are not allowed and if needed in a future version, that version will not be backwards compatible.I know nested divs is not currently listed as a feature per se but if we continue with that approach into CR, I would like to mark it at risk to allow potentially removing it based on implementation feedback.
Originally posted by @cconcolato in #216 (review)
The text was updated successfully, but these errors were encountered: