- From: <bugzilla@jessica.w3.org>
- Date: Thu, 25 Oct 2012 05:53:42 +0000
- To: public-webplatform-bugs@w3.org
- Message-ID: <bug-19499-5733-1YXXmp0oE8@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19499 Alex Komoroske <komoroske@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |komoroske@google.com --- Comment #1 from Alex Komoroske <komoroske@google.com> --- Technically, the (extremely confusing and only partial) way this works today is that the markup element article is supposed to specify the DOM Interface it uses (in most cases this is HTMLElement, but for some elements with a different interface, like Canvas, it will be something else). Then attributes should also specify which DOM Interface they apply to. This implicitly would allow us to then print out all of the applicable attributes on the Markup Element page. However, the bit where we print out all attributes isn't implemented yet today. Part of the reason is that figuring out how properties + attributes interact is hard. Should we have a Markup Attribute article AND a API_Object_Property article for each thing that is both an attribute and property? If we don't, then how should we automatically list all applicable attributes? I think we should think hard about how to improve this. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 25 October 2012 05:53:43 UTC