- From: <bugzilla@jessica.w3.org>
- Date: Thu, 19 Apr 2012 23:05:50 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16805 Summary: Hi, I would change the Boolean attributes definition, to be able to make true/false assignements. In that way, you can make easier to program a dinamic web-form: is_modifying="=false" disable${is_modifying} so that just substituting would make available t Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Specification: http://www.w3.org/TR/2012/WD-html5-20120329/index.html Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Hi, I would change the Boolean attributes definition, to be able to make true/false assignements. In that way, you can make easier to program a dinamic web-form: is_modifying="=false" disable${is_modifying} so that just substituting would make available the activation, instead of having to put a if/else statement. In this way you can guarantee backwards compatibility and make available easier ways to program. Boolean attributes Posted from: 95.16.113.20 User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/11.10 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 -- Configure bugmail: https://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 Thursday, 19 April 2012 23:05:52 UTC