[css-ui-4] Issue refactoring

Author: frivoal

css-ui-4/Overview.bs

@@ -1838,17 +1838,6 @@ Animation type: discrete
 
 		Elements other than form controls must be rendered as if ''appearance/none'' had been specified.
 
-		Issue: On some elements, setting some properties inhibits ''appearance: auto''.
-		For instance, even if 'appearance' is ''appearance/auto'',
-		buttons lose their native appearance when a 'border' is set.
-		This is not in contradiction with this part of the spec,
-		since ''appearance: auto'' only means
-		UAs <em>may</em> use a native appearance,
-		but for greater interoperability,
-		it would be good to document
-		which properties on which elements
-		have this effect.
-
 	<dt><dfn>button</dfn>
 	<dd>
 		The element is rendered with the look and feel of a push button,
@@ -1871,17 +1860,9 @@ Animation type: discrete
 
 		Issue: It is possible that for compat reasons,
 		some of these values need to be promoted to being full blown values
-		with actual effects, like ''button''.
-
-		Issue: It is possible that some of these values need to have some side effects on some elements.
-		For example, for a while it seemed that we might need all values other than ''appearance/none'',
-		when applied to the <{select}> element,
-		to reserve space for the arrow on the right side indicating that the list will be expanded if the element is clicked,
-		but only the ''menu-list'' value would actually display that arrow.
-		<a href="https://github.com/w3c/csswg-drafts/issues/1250#issuecomment-434554323">Mozilla has concluded</a>
-		that this particular quirk was not necessary,
-		but if anything of the sort is needed, it should be documented here.
-		Hopefully we don't need any.
+		with effects on arbitrary elements like ''button'',
+		or that
+		some of these values need to have some side effects on some form controls.
 
 
 </dl>
@@ -1959,11 +1940,6 @@ what needs to be preserved.
 UAs should include in their User Agent stylesheet style rules
 to give form controls a recognizable shape when 'appearance' is ''appearance/none''.
 
-Issue: Documenting what UAs need to put in their UA stylesheet would be good.
-It could go in this specification,
-as an appendix,
-but its long term how is probably the HTML specification.
-
 Note: Authors may therefore need to override these UA style rules to get the styling
 they intended.
 
@@ -2041,6 +2017,23 @@ as a [=legacy name alias=] of 'appearance'.
 <h3 id=control-specific-rules>
 Form Control Specific Rules</h3>
 
+Issue: Maybe some or all of this section
+should be moved to the [[HTML]] spec
+at some point.
+
+Issue: On some elements, setting some properties inhibits ''appearance: auto''.
+For instance, even if 'appearance' is ''appearance/auto'',
+buttons lose their native appearance when a 'border' is set.
+This is not in contradiction with the definition of ''appearance/auto'',
+since ''appearance: auto'' only means
+UAs <em>may</em> use a native appearance,
+but for greater interoperability,
+it would be good to document
+which properties on which elements
+have this effect.
+
+Issue: Documenting what UAs need to put in their UA stylesheet would be good.
+
 <h4 id=input-rules>
 Single-Line Text Input Controls</h4>