Trim whitespaces

Author: saschanaz

index.html

@@ -6013,7 +6013,7 @@ <h5>Note regarding the ARIA 1.1 <code>none</code> role.</h5>
         <p>In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>option</rref> in a <rref>listbox</rref>, and if it does, the user agent MUST ensure the following conditions are met before providing an implicit value:</p>
         <ul>
           <li>The value of <pref>aria-multiselectable</pref> on the <rref>listbox</rref> is <code>false</code> or <code>undefined</code>.</li>
-          <li>None of the <rref>option</rref> elements in the <rref>listbox</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>  
+          <li>None of the <rref>option</rref> elements in the <rref>listbox</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>
         </ul>
         <p>
           If a user agent provides an implicit <sref>aria-selected</sref> value for an <rref>option</rref>, the value SHOULD be <code>true</code> if the <rref>option</rref> has DOM focus or the <rref>listbox</rref> has DOM focus and the <rref>option</rref> is referenced by <pref>aria-activedescendant</pref>.
@@ -8704,7 +8704,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
         <p>In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>tab</rref> in a <rref>tablist</rref>, and if it does, the user agent MUST ensure the following conditions are met before providing an implicit value:</p>
         <ul>
           <li>The value of <pref>aria-multiselectable</pref> on the <rref>tablist</rref> is <code>false</code> or <code>undefined</code>.</li>
-          <li>None of the <rref>tab</rref> elements in the <rref>tablist</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-expanded</sref>.</li>  
+          <li>None of the <rref>tab</rref> elements in the <rref>tablist</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-expanded</sref>.</li>
         </ul>
 			</div>
 			<table class="role-features">
@@ -9917,7 +9917,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
         <p>In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>treeitem</rref> in a <rref>tree</rref>, and if it does, the user agent MUST ensure the following conditions are met before providing an implicit value:</p>
         <ul>
           <li>The value of <pref>aria-multiselectable</pref> on the <rref>tree</rref> is <code>false</code> or <code>undefined</code>.</li>
-          <li>None of the <rref>treeitem</rref> elements in the <rref>tree</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>  
+          <li>None of the <rref>treeitem</rref> elements in the <rref>tree</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>
         </ul>
         <p>
           If a user agent provides an implicit <sref>aria-selected</sref> value for a <rref>treeitem</rref>, the value SHOULD be <code>true</code> if the <rref>treeitem</rref> has DOM focus or the <rref>tree</rref> has DOM focus and the <rref>treeitem</rref> is referenced by <pref>aria-activedescendant</pref>.
@@ -10228,33 +10228,33 @@ <h3>Value</h3>
 		<h2>ARIA Attributes</h2>
 		<section id="enumerated-attribute-values">
 			<h3>Multi-value Attribute Values</h3>
-			<p>When the ARIA attribute definition includes a table listing the attribute's allowed <span>values</span>, 
-			that attribute is a multi-value nullable attribute. 
+			<p>When the ARIA attribute definition includes a table listing the attribute's allowed <span>values</span>,
+			that attribute is a multi-value nullable attribute.
 			Each value in the table is a keyword for the attribute, mapping to a state of the same name. </p>
 		</section>
 		<section id="idl-reflection-attribute-values">
 			<h3>IDL reflection of ARIA attributes</h3>
-			<p>All ARIA attributes reflect in IDL as [=nullable type|nullable=] {{DOMString}} attributes. 
+			<p>All ARIA attributes reflect in IDL as [=nullable type|nullable=] {{DOMString}} attributes.
 			This includes the boolean-like <a href="#valuetype_true-false">true/false</a> type, and all other ARIA attributes.</p>
-			<p>Default values from the ARIA values tables MUST NOT reflect to IDL as the 
-			<a data-cite="html/common-microsyntaxes.html#missing-value-default">missing value default</a> or the 
-			<a data-cite="html/common-microsyntaxes.html#invalid-value-default">invalid value default</a> for the attribute. 
-			On getting, a missing ARIA attribute will return <code>null</code>. ARIA attributes are not validated on get. 
+			<p>Default values from the ARIA values tables MUST NOT reflect to IDL as the
+			<a data-cite="html/common-microsyntaxes.html#missing-value-default">missing value default</a> or the
+			<a data-cite="html/common-microsyntaxes.html#invalid-value-default">invalid value default</a> for the attribute.
+			On getting, a missing ARIA attribute will return <code>null</code>. ARIA attributes are not validated on get.
 			If an ARIA value is invalid, on getting, it will return its set value as a literal string, and will not return an invalid value default.</p>
 		</section>
 		<section id="os-aapi-attribute-mapping">
 			<h3>Operating System Accessibility API mapping of multi-value ARIA attributes</h3>
-			<p>Unlike IDL reflection, operating system accessibility API mappings of ARIA attributes can have defaults. 
-			Any default values from the ARIA values tables are exposed to the operating system accessibility API as described in 
+			<p>Unlike IDL reflection, operating system accessibility API mappings of ARIA attributes can have defaults.
+			Any default values from the ARIA values tables are exposed to the operating system accessibility API as described in
 			[[[#supportedState]]], and in [[[CORE-AAM]]].</p>
 		</section>
 		<section id="enumerated-attribute-values-html">
 			<h3>ARIA nullable DOMString Attributes</h3>
 			<p>As noted in [[[#typemapping]]], attributes are included in host languages, and the syntax for representation of WAI-ARIA types is governed by the host language.</p>
 			<p>The following algorithm should be used for ARIA nullable {{DOMString}} attributes in HTML:</p>
-			<p>On getting, if the corresponding content attribute is not present, then the IDL attribute must return null, 
-			otherwise, the IDL attribute must get the value in a transparent, case-preserving manner. 
-			On setting, if the new value is null, the content attribute must be removed, and otherwise, 
+			<p>On getting, if the corresponding content attribute is not present, then the IDL attribute must return null,
+			otherwise, the IDL attribute must get the value in a transparent, case-preserving manner.
+			On setting, if the new value is null, the content attribute must be removed, and otherwise,
 			the content attribute must be set to the specified new value in a transparent, case-preserving manner.</p>
 			<p class="note">
 			Note: As of ARIA 1.2, all ARIA attributes exposed via IDL are defined as nullable {{DOMStrings}}. This matches the current implementation of all major rendering engines. This specification change should result in no implementation changes; it will merely represent the current reality of web engines.