- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 10 Nov 2016 17:31:36 -0800
- To: Travis Leithead <travis.leithead@microsoft.com>
- Cc: "Hodges, Jeff" <jeff.hodges@paypal.com>, "spec-prod@w3.org" <spec-prod@w3.org>, Arron Eicholz <arronei@microsoft.com>
On Thu, Nov 10, 2016 at 5:07 PM, Travis Leithead <travis.leithead@microsoft.com> wrote: > Funny, this hit the W3C HTML spec as well. My case was: https://github.com/travisleithead/html/commit/b59f37a5056dfa1875328d428bcc1ca49d198f53#diff-eb18865acfd94500fe999f8128227ed6 > (in response to https://github.com/w3c/html/issues/707) > > Where an ancestor dfn-for='....' was inheriting down to a <dfn element>...<dfn>. However, it _is_ legitimate for an element to have a for attribute, so I don't see the problem? In the above commit, I fix the issue by moving the ancestor definition to locally-needed terms, but I don't think I should have to do that... Elements are specifically marked in Bikeshed as *not* using the `for` attribute currently (thus the error). What's your use-case for giving them one? ~TJ
Received on Friday, 11 November 2016 01:32:28 UTC