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 12900 - A global attribute "contentaddedbyeditor" would be incredibly useful when testing for accessibility. It would be great to be able to distinguish between the template a template developer has produced, and the content which an editor then fills into the t
Summary: A global attribute "contentaddedbyeditor" would be incredibly useful when tes...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-06-07 10:23 UTC by contributor
Modified: 2011-08-04 05:14 UTC (History)
7 users (show)

See Also:


Attachments

Description contributor 2011-06-07 10:23:39 UTC
Specification: http://www.w3.org/TR/html5/
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
A global attribute "contentaddedbyeditor" would be incredibly useful when
testing for accessibility.  It would be great to be able to distinguish
between the template a template developer has produced, and the content which
an editor then fills into the template.  If this could be achieved by the
addition of a global attribute then a template developer could test their
parts of a published page, whilst the editor could test their parts of a
published page.  

I have suggested a global attribute rather than use data-contentaddedbyeditor
as each developer might come up with their own version of
data-contentaddedbyeditor which would not be good for standardisation.	    

Posted from: 81.230.70.95
User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-us) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4
Comment 1 Tab Atkins Jr. 2011-06-08 07:10:22 UTC
Template developers can test their templates by filling them with an empty page.  Editors can test their page content by squirting it into a trivial template.

I don't see any particular need for HTML to help with either of these tasks, as they're both pretty trivial.
Comment 2 Aryeh Gregor 2011-06-24 21:43:19 UTC
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: Additional Information Needed
Change Description: no spec change
Rationale: I don't understand the use-case.  Please explain what this attribute would actually be used for in practice.  If possible, please give examples of real-world web pages or software that would use it, and explain exactly how they would use it, and what problems they face without it.  Note that if the attribute is only intended for use by internal processing tools, and not browsers or search engines or other things that aren't under the author's control, there's no need for standardization -- that's exactly what data-* is meant for.
Comment 3 Michael[tm] Smith 2011-08-04 05:14:08 UTC
mass-move component to LC1