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 16805 - Change Boolean definition to do true/false assignments easier
Summary: Change Boolean definition to do true/false assignments easier
Status: RESOLVED DUPLICATE of bug 12148
Alias: None
Product: HTML WG
Classification: Unclassified
Component: 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:
Depends on:
Blocks:
 
Reported: 2012-04-19 23:05 UTC by contributor
Modified: 2012-04-21 07:16 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2012-04-19 23:05:48 UTC 
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
Comment 1 Javier Domingo 2012-04-19 23:30:05 UTC 
This can be achieved by something like:

set modify="disable" #or whatever to set the variable

<input type="text" name="field" $modify>

Although it can be still interesting to have that true/false availability
Comment 2 Anne 2012-04-21 07:16:09 UTC 

*** This bug has been marked as a duplicate of bug 12148 ***