This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19499 - Template for markup elements should have dedicated section for attributes
Summary: Template for markup elements should have dedicated section for attributes
Status: RESOLVED MOVED
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: content (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Alex Komoroske
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-12 09:19 UTC by Dominique Hazael-Massieux
Modified: 2013-02-23 17:21 UTC (History)
2 users (show)

See Also:

Attachments

Description Dominique Hazael-Massieux 2012-10-12 09:19:31 UTC 
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)
Comment 1 Alex Komoroske 2012-10-25 05:53:42 UTC 
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.
Comment 2 Jonathan Garbee 2013-02-23 17:21:44 UTC 
New location: http://project.webplatform.org/tmpl/issues/3