Skip to content

Commit 939e370

Browse files
nt1mnt1m
committed
[css-forms-1][editorial] Fix up indentation
1 parent ba91d71 commit 939e370

File tree

1 file changed

+115
-115
lines changed

1 file changed

+115
-115
lines changed

‎css-forms-1/Overview.bs

+115-115
Original file line numberDiff line numberDiff line change
@@ -617,54 +617,54 @@ spec:css-forms-1; type:value; for:/; text:::placeholder
617617

618618
## Switching form control sizing: the 'field-sizing' property ## {#field-sizing}
619619

620-
<pre class=propdef>
621-
Name: field-sizing
622-
Value: fixed | content
623-
Initial: ''field-sizing/fixed''
624-
Applies to: [=elements with default preferred size=]
625-
Inherited: no
626-
Percentages: N/A
627-
Computed Value: as specified
628-
Canonical order: per grammar
629-
Animation type: discrete
630-
</pre>
631-
632-
For the purpose of this specification,
633-
an <dfn export>element with default preferred size</dfn> is an element
634-
whose [=intrinsic size=] is fixed regardless of the size of its content.
635-
The host language defines which elements are applicable to it.
636-
For example, in HTML <{textarea}> is an [=element with default preferred size=].
637-
638-
<dl dfn-type=value dfn-for=field-sizing>
639-
<dt><dfn>fixed</dfn>
640-
<dd>
641-
For [=element with default preferred size=],
642-
the UA must set the [=intrinsic size=]
643-
to the default preferred size defined by the host language for that element.
644-
Otherwise, the UA must behave the same as ''field-sizing/content''.
645-
<dt><dfn>content</dfn>
646-
<dd>
647-
The UA must determine the element's [=intrinsic size=] based on its content,
648-
and must ignore any default preferred size defined by the host language for that element.
649-
If the element is an [=element with default preferred size=] and
650-
is listed in [[CSS-SIZING-3#min-content-zero|compressible replaced elements]],
651-
the UA must stop treating the element as a replaced element for [=min-content contribution=].
652-
</dl>
653-
654-
<div class="example">
655-
For instance, <{textarea}> has a fixed size regardless of its content by default:
656-
657-
<span class="fake-textarea auto">&#x23B8;</span>
658-
<span class="fake-textarea auto">The quick brown fox jumps over the lazy dog.</span>
659-
660-
If ''field-sizing: content'' is applied, the size of the former should fit to a text caret.
661-
<span class="fake-textarea">&#x23B8;</span>
662-
663-
If ''field-sizing: content'' is applied and its width property has a fixed value like ''width: 10em'',
664-
the element height depends on the number of the content lines:
665-
666-
<span class="fake-textarea normal">The quick brown fox jumps over the lazy dog.&#x23B8;</span>
667-
</div>
620+
<pre class=propdef>
621+
Name: field-sizing
622+
Value: fixed | content
623+
Initial: ''field-sizing/fixed''
624+
Applies to: [=elements with default preferred size=]
625+
Inherited: no
626+
Percentages: N/A
627+
Computed Value: as specified
628+
Canonical order: per grammar
629+
Animation type: discrete
630+
</pre>
631+
632+
For the purpose of this specification,
633+
an <dfn export>element with default preferred size</dfn> is an element
634+
whose [=intrinsic size=] is fixed regardless of the size of its content.
635+
The host language defines which elements are applicable to it.
636+
For example, in HTML <{textarea}> is an [=element with default preferred size=].
637+
638+
<dl dfn-type=value dfn-for=field-sizing>
639+
<dt><dfn>fixed</dfn>
640+
<dd>
641+
For [=element with default preferred size=],
642+
the UA must set the [=intrinsic size=]
643+
to the default preferred size defined by the host language for that element.
644+
Otherwise, the UA must behave the same as ''field-sizing/content''.
645+
<dt><dfn>content</dfn>
646+
<dd>
647+
The UA must determine the element's [=intrinsic size=] based on its content,
648+
and must ignore any default preferred size defined by the host language for that element.
649+
If the element is an [=element with default preferred size=] and
650+
is listed in [[CSS-SIZING-3#min-content-zero|compressible replaced elements]],
651+
the UA must stop treating the element as a replaced element for [=min-content contribution=].
652+
</dl>
653+
654+
<div class="example">
655+
For instance, <{textarea}> has a fixed size regardless of its content by default:
656+
657+
<span class="fake-textarea auto">&#x23B8;</span>
658+
<span class="fake-textarea auto">The quick brown fox jumps over the lazy dog.</span>
659+
660+
If ''field-sizing: content'' is applied, the size of the former should fit to a text caret.
661+
<span class="fake-textarea">&#x23B8;</span>
662+
663+
If ''field-sizing: content'' is applied and its width property has a fixed value like ''width: 10em'',
664+
the element height depends on the number of the content lines:
665+
666+
<span class="fake-textarea normal">The quick brown fox jumps over the lazy dog.&#x23B8;</span>
667+
</div>
668668

669669
## Changing the Orientation of a [=Slider-Like Control=]: ''slider-orientation'' ## {#slider-orientation}
670670

@@ -705,73 +705,73 @@ spec:css-forms-1; type:value; for:/; text:::placeholder
705705

706706
## Obscuring sensitive input: the 'input-security' property ## {#input-security}
707707

708-
Issue: The CSSWG has agreed that
709-
while we believe that providing this piece of functionality to users is important,
710-
doing it via CSS+JS is the wrong approach,
711-
and that instead it should be built into user agents:
712-
this needs to work consistently from site to site for it to be discoverable and understandable by users,
713-
this needs to work even when JS is turned off,
714-
and this needs to have consistently solid accessibility…
715-
We therefore intend to remove this from the specification,
716-
and instead, we would like to see this behavior specified in the HTML specification
717-
as part of the interaction model of password fields.
718-
Holding off deleting until the situation with HTML is clarified.
719-
See
720-
<a href="https://github.com/w3c/csswg-drafts/issues/6788">https://github.com/w3c/csswg-drafts/issues/6788</a>
721-
and
722-
<a href="https://github.com/whatwg/html/issues/7293">https://github.com/whatwg/html/issues/7293</a>.
723-
724-
<pre class=propdef>
725-
Name: input-security
726-
Value: auto | none
727-
Initial: ''input-security/auto''
728-
Applies to: [=sensitive text inputs=]
729-
Inherited: no
730-
Percentages: N/A
731-
Computed Value: as specified
732-
Canonical order: per grammar
733-
Animation type: by computed value type
734-
</pre>
735-
736-
For the purpose of this specification,
737-
a <dfn export>sensitive text input</dfn> is
738-
a text input whose purpose is to accept sensitive input,
739-
as defined by the host language.
740-
For example, in HTML <{input/type/password|&lt;input type=password&gt;}> is a [=sensitive text input=].
741-
742-
By default, user agents obscure the contents of [=sensitive text inputs=]
743-
in order to prevent onlookers from seeing it.
744-
Users may wish to temporarily disable this obscuring
745-
in order to confirm that they've typed their sensitive information correctly.
746-
The ''input-security'' property may be used by authors
747-
to enable or disable this obscuring.
748-
749-
<dl dfn-type=value dfn-for=input-security>
750-
<dt><dfn>none</dfn>
751-
<dd>
752-
The UA must not obscure the text in the control,
753-
so that it can be read by the user.
754-
<dt><dfn>auto</dfn>
755-
<dd>
756-
The UA should obscure the text in the control,
757-
so that it cannot be read by the user.
758-
</dl>
759-
760-
While the exact mechanism by which user agents obscure the text in the control is undefined, user agents typically obscure [=sensitive text inputs=] by replacing each character with some suitable replacement such as U+002A ASTERISK (*) or U+25CF BLACK CIRCLE (●).
761-
762-
<div class="example">
763-
For instance, given this style sheet
764-
<pre><code class="lang-css">
765-
input[type=password] {
766-
input-security: auto;
767-
}</code></pre>
768-
and this HTML
769-
<pre><code class="lang-html">
770-
&lt;input type=password value=MySecret794>
771-
</code></pre>
772-
a user agent might render the <{input/type/password|&lt;input type=password&gt;}> like so:
773-
<span class=fake-input-type-password>●●●●●●●●●●●</span>
774-
</div>
708+
Issue: The CSSWG has agreed that
709+
while we believe that providing this piece of functionality to users is important,
710+
doing it via CSS+JS is the wrong approach,
711+
and that instead it should be built into user agents:
712+
this needs to work consistently from site to site for it to be discoverable and understandable by users,
713+
this needs to work even when JS is turned off,
714+
and this needs to have consistently solid accessibility…
715+
We therefore intend to remove this from the specification,
716+
and instead, we would like to see this behavior specified in the HTML specification
717+
as part of the interaction model of password fields.
718+
Holding off deleting until the situation with HTML is clarified.
719+
See
720+
<a href="https://github.com/w3c/csswg-drafts/issues/6788">https://github.com/w3c/csswg-drafts/issues/6788</a>
721+
and
722+
<a href="https://github.com/whatwg/html/issues/7293">https://github.com/whatwg/html/issues/7293</a>.
723+
724+
<pre class=propdef>
725+
Name: input-security
726+
Value: auto | none
727+
Initial: ''input-security/auto''
728+
Applies to: [=sensitive text inputs=]
729+
Inherited: no
730+
Percentages: N/A
731+
Computed Value: as specified
732+
Canonical order: per grammar
733+
Animation type: by computed value type
734+
</pre>
735+
736+
For the purpose of this specification,
737+
a <dfn export>sensitive text input</dfn> is
738+
a text input whose purpose is to accept sensitive input,
739+
as defined by the host language.
740+
For example, in HTML <{input/type/password|&lt;input type=password&gt;}> is a [=sensitive text input=].
741+
742+
By default, user agents obscure the contents of [=sensitive text inputs=]
743+
in order to prevent onlookers from seeing it.
744+
Users may wish to temporarily disable this obscuring
745+
in order to confirm that they've typed their sensitive information correctly.
746+
The ''input-security'' property may be used by authors
747+
to enable or disable this obscuring.
748+
749+
<dl dfn-type=value dfn-for=input-security>
750+
<dt><dfn>none</dfn>
751+
<dd>
752+
The UA must not obscure the text in the control,
753+
so that it can be read by the user.
754+
<dt><dfn>auto</dfn>
755+
<dd>
756+
The UA should obscure the text in the control,
757+
so that it cannot be read by the user.
758+
</dl>
759+
760+
While the exact mechanism by which user agents obscure the text in the control is undefined, user agents typically obscure [=sensitive text inputs=] by replacing each character with some suitable replacement such as U+002A ASTERISK (*) or U+25CF BLACK CIRCLE (●).
761+
762+
<div class="example">
763+
For instance, given this style sheet
764+
<pre><code class="lang-css">
765+
input[type=password] {
766+
input-security: auto;
767+
}</code></pre>
768+
and this HTML
769+
<pre><code class="lang-html">
770+
&lt;input type=password value=MySecret794>
771+
</code></pre>
772+
a user agent might render the <{input/type/password|&lt;input type=password&gt;}> like so:
773+
<span class=fake-input-type-password>●●●●●●●●●●●</span>
774+
</div>
775775

776776
<h2 class="no-num non-normative" id="basic-appearance-stylesheet">Appendix A: Basic Appearance User Agent Stylesheet</h2>
777777

0 commit comments

Comments
 (0)