Hopiu/angular.js
1
0
Fork 0
mirror of https://github.com/Hopiu/angular.js.git synced 2026-03-16 23:30:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(booleanAttrs): improve grammar and clarity

Browse source 
Closes #4392
This commit is contained in:
Dave Peticolas 2013-10-12 17:33:45 -07:00 committed by Pete Bacon Darwin
parent 27519e9a33
commit e79a20e1ca
1 changed files with 20 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
src/ng/directive/booleanAttrs.js
View file

@ -147,10 +147,10 @@
* </div>
* </pre>
*
* The HTML specs do not require browsers to preserve the values of special attributes
* such as disabled. (The presence of them means true and absence means false)
* This prevents the Angular compiler from correctly retrieving the binding expression.
* To solve this problem, we introduce the `ngDisabled` directive.
* The HTML specification does not require browsers to preserve the values of boolean attributes
* such as disabled. (Their presence means true and their absence means false.)
* This prevents the Angular compiler from retrieving the binding expression.
* The `ngDisabled` directive solves this problem for the `disabled` attribute.
*
* @example
<doc:example>
@ -179,10 +179,10 @@
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as checked.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
* To solve this problem, we introduce the `ngChecked` directive.
* The HTML specification does not require browsers to preserve the values of boolean attributes
* such as checked. (Their presence means true and their absence means false.)
* This prevents the Angular compiler from retrieving the binding expression.
* The `ngChecked` directive solves this problem for the `checked` attribute.
* @example
<doc:example>
<doc:source>
@ -210,10 +210,10 @@
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as readonly.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
* To solve this problem, we introduce the `ngReadonly` directive.
* The HTML specification does not require browsers to preserve the values of boolean attributes
* such as readonly. (Their presence means true and their absence means false.)
* This prevents the Angular compiler from retrieving the binding expression.
* The `ngReadonly` directive solves this problem for the `readonly` attribute.
* @example
<doc:example>
<doc:source>
@ -241,10 +241,10 @@
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as selected.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
* To solve this problem, we introduced the `ngSelected` directive.
* The HTML specification does not require browsers to preserve the values of boolean attributes
* such as selected. (Their presence means true and their absence means false.)
* This prevents the Angular compiler from retrieving the binding expression.
* The `ngSelected` directive solves this problem for the `selected` atttribute.
* @example
<doc:example>
<doc:source>
@ -274,10 +274,10 @@
* @restrict A
*
* @description
* The HTML specs do not require browsers to preserve the special attributes such as open.
* (The presence of them means true and absence means false)
* This prevents the angular compiler from correctly retrieving the binding expression.
* To solve this problem, we introduce the `ngOpen` directive.
* The HTML specification does not require browsers to preserve the values of boolean attributes
* such as open. (Their presence means true and their absence means false.)
* This prevents the Angular compiler from retrieving the binding expression.
* The `ngOpen` directive solves this problem for the `open` attribute.
*
* @example
<doc:example>