- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 26 Dec 2009 02:01:33 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8552 Summary: Remove the Progress Element Product: HTML WG Version: unspecified Platform: Macintosh OS/Version: Mac System 9.x Status: NEW Severity: normal Priority: P2 Component: HTML5 spec proposals AssignedTo: dave.null@w3.org ReportedBy: shelleyp@burningbird.net QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org The progress element is to be use to mark the progress of a specific task, but there is no way to easily differentiate what the task is. Automations would be reduced to scraping the page and attempting to derive the task based on page structure, rather than based on sound semantic principle. There are metadata approaches to marking up both task, and its associated progress. People can use RDFa to mark both, using sound and tested techniques. With the use of RDFa, applications won't need complicated and error-prone algorithms to try and derive the task-progress pair. In addition, people can also use Microformats, either with existing Microformat vocabularies, or ones to be introduced into the future. A further reason to no longer keep the progress element is that there's nothing associated with the progress element that will make web application developer tasks any easier. It's just as simple to use existing progress indicator functionality built into existing JavaScript, Canvas, and SVG libraries, as it would be to use this element. If anything, the use of this element could require more work, in order to change existing libraries to use a specific type of element, rather than the more general div or span elements most likely used today. The addition of a progress element will also require modification to HTML editors, as well as browsers, and as far as I've been able to determine, other than using it more or less as an unknown element, there is no implementation for this element. Lastly, the description for progress is overly complicated--mixing HTML syntax and user agent parsing directions, as well as proving an inordinate number of somewhat confusing rules and regulations for the progress element's conforming use. This is going to make it more likely, rather than less, that the progress element will be used by web page authors and designers correctly. It would be best to remove the element, and depend on existing semantic markup techniques, such as RDF and Microformats to mark up semantics, and existing JavaScript libraries and graphics capabilities such as Canvas, CSS, and SVG, to provide presentation. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 26 December 2009 02:01:34 UTC