19499 2012-10-12 09:19:31 +0000 Template for markup elements should have dedicated section for attributes 2013-02-23 17:21:44 +0000 1 1 1 Unclassified webplatform.org content unspecified PC Linux RESOLVED MOVED P2 normal --- 1 dom komoroske jonathan komoroske public-webplatform-bugs oldest_to_newest 76074 0 dom 2012-10-12 09:19:31 +0000 When documenting a markup element, there should be a semantic way to document its attributes; it isn't the case today (at least for HTML elements) 77090 1 komoroske 2012-10-25 05:53:42 +0000 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. 83627 2 jonathan 2013-02-23 17:21:44 +0000 New location: http://project.webplatform.org/tmpl/issues/3