This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The aside element should accept the for attribute (as does the label element) so that it can identify itself as related to something on the page (e.g. the main article) even if it is located elsewhere (e.g. in a side panel). The spec currently says that aside is always related to the content that contains the aside element, and it's not clear whether or how the author could then position it in a side panel or navigation area. There may be other elements to which this would also apply.
mass-move component to LC1
(In reply to comment #0) > The aside element should accept the for attribute (as does the label element) > so that it can identify itself as related to something on the page (e.g. the > main article) even if it is located elsewhere (e.g. in a side panel). The spec > currently says that aside is always related to the content that contains the > aside element, and it's not clear whether or how the author could then position > it in a side panel or navigation area. CSS, perhaps using a feature such as the proposed move-to property: http://www.w3.org/TR/css3-content/#moving @for might be useful as a bridging technology, but @aria-flowto could probably do this work already: http://www.w3.org/TR/wai-aria/states_and_properties#aria-flowto -- Benjamin Hawkes-Lewis
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: You can use CSS.