Skip to content

Commit ea62c9e

Browse files
committed
[css-ui-4] Minor rephasings and typo fixing
1 parent 8373e1a commit ea62c9e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

css-ui-4/Overview.bs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1791,7 +1791,7 @@ This specification introduces the 'appearance' property
17911791
to provide some control over this behavior.
17921792
In particular, using ''appearance: none'' allows authors
17931793
to suppress the native style of form controls,
1794-
so that CSS can be used to fully restyle them.
1794+
so that CSS can be used to restyle them.
17951795

17961796
<pre class="propdef">
17971797
Name: appearance, -webkit-appearance
@@ -1840,7 +1840,7 @@ Animation type: discrete
18401840

18411841
Issue: On some elements, setting some properties inhibits ''appearance: auto''.
18421842
For instance, even if 'appearance' is ''appearance/auto'',
1843-
buttons lose they native appearance when a 'border' is set.
1843+
buttons lose their native appearance when a 'border' is set.
18441844
This is not in contradiction with this part of the spec,
18451845
since ''appearance: auto'' only means
18461846
UAs <em>may</em> use a native appearance,
@@ -1852,7 +1852,7 @@ Animation type: discrete
18521852
<dt><dfn>button</dfn>
18531853
<dd>
18541854
The element is rendered with the look and feel of a push button,
1855-
similar to the rendering of the [[HTML]] <{button}> element.
1855+
similar to the ''appearance: auto'' rendering of the [[HTML]] <{button}> element.
18561856

18571857
Issue: Are there some form controls or other replaced elements
18581858
on which this value should be a no&#x2011;op?

0 commit comments

Comments
 (0)