- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 28 Dec 2009 23:58:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8552 --- Comment #11 from Maciej Stachowiak <mjs@apple.com> 2009-12-28 23:58:45 --- (In reply to comment #10) > from #1: > > The <progress> element is the only way to get a progress bar that matches the > native look and feel of the platform. > I don't think this kind of reason warrants a new element type. It's a > presentational need and should be solved by styling. Indeed, we're awaiting the > appearance property in CSS which will do exactly that. Sure, you could try to make a styling-only solution. However, an appearance property would be hard to apply by itself, since a progress indicator has many visual states (the different possible progress levels, multiple indetermediate states, and different horizontal and vertical states. All told it would take hundreds of different appearance values unless the appearance property knew how to be reactive to some aspect of the element state. Whether or not a styling-level solution could get the appearance right, controls commonly found in application user interface, it seems to me we should provide a single solution that provides the appearance, behavior, semantics and accessibility aspects of a progress indicator, rather than making authors implement each separately by hand. > Or is there actually some semantic rationale for progress? Is it like WHATWG's > idea of http://www.w3.org/TR/xforms/#ui-range The HTML5 equivalent of this is <input type=range>, not <progress>. > (which, BTW, shows the quoted statement to be false)? No, a range input is completely different from a progress indicator. A range input is typically rendered as a slider control. A slider has a thumb that lets the user select a value. A progress bar looks completely different, in all GUI toolkits with which I am familiar. The XForms section you link even has a sample rendering which is very clearly not a progress bar but a slider. -- 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 Monday, 28 December 2009 23:58:48 UTC