- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 29 Dec 2009 14:18:58 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8552 --- Comment #12 from Krzysztof MaczyĆski <1981km@gmail.com> 2009-12-29 14:18:57 --- While the best mapping of XForms' range to HTML5 would indeed most often be adorned input (thx for reminding; I check on the proliferation of input/@type values only occasionally), the reverse mapping would give range (used with read-only MIP) for HTML5's proposed progress as well. Genericity of XForms' set of controls (device independence, presentation agnosticism, features nice for a11y, l10n and m12n) is a better approach. HTML is not a UI (actually even GUI) language and it would be both unwise and grotesque (given the basis of HTML forms' legacy) to extend it too much in that direction. I see two very viable styling solutions, both author friendly. One is functional notations in appearance values capable of expressing the necessary facets you mention. The other is a binding (see http://lists.w3.org/Archives/Public/public-html/2009Sep/0739.html for something similar). Thoughts, preferences, anybody? Even if progress is included, I strongly prefer a styling solution which would also be applicable beyond HTML5 (indeed, XForms comes promptly to mind). -- 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 Tuesday, 29 December 2009 14:18:59 UTC