- From: chaals <notifications@github.com>
- Date: Fri, 26 May 2017 06:50:50 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 May 2017 13:51:25 UTC
Can you please explain the "defn" issue? I will raise it on the spec when I am clear that I understand what it is, but right now, I do not. My guess is that you mean we should expand the model of `dfn` from phrasing content to flow content, allowing it to include headings, lists, etc. But since the element is used to identify the term being defined - i.e. just the words which are being defined - I find it hard to imagine a case where the words will run across elements other than phrasing content: links, `em`/`s`/`var`/etc, and even things like `audio`. I'm inclined to suggest that the proposed change, if I have understood it, be rejected… How fallback content included in elements like `audio` works in the context of phrasing content *may* be poorly defined, although I haven't looked at that carefully myself. -- 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/119#issuecomment-304287389
Received on Friday, 26 May 2017 13:51:25 UTC