- From: Travis Leithead <notifications@github.com>
- Date: Tue, 11 Sep 2018 11:16:17 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 September 2018 18:16:39 UTC
> doesn't that increase the likelihood that at any time we want to introduce it for custom attributes later we will find it more difficult? @chaals see annevk's comment about "custom global attributes" above -- where those would likely require a hyphen to avoid conflicting with known attributes (just like custom elements requires today). So, I don't think we need to worry about future conflicts with custom attributes. As noted above, new built-in attributes will need to be added with care. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/244#issuecomment-420369688
Received on Tuesday, 11 September 2018 18:16:39 UTC