[css-overflow] Spec clean-up

Make bikeshed happy by fixing the problems it found

Author: frivoal

css-overflow/Overview.bs

@@ -11,9 +11,12 @@ Previous version: https://www.w3.org/TR/css-overflow-3/
 Editor: L. David Baron, Mozilla https://www.mozilla.org/, https://dbaron.org/
 Editor: Florian Rivoal, On behalf of Bloomberg, http://florian.rivoal.net/
 Abstract: This module contains the features of CSS relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).  In interactive media, it describes features that allow the overflow from a fixed size container to be handled by pagination (displaying one page at a time).  It also describes features, applying to all visual media, that allow the contents of an element to be spread across multiple fragments, allowing the contents to flow across multiple regions or to have different styles for different fragments.
+Ignored Terms: scroll
 </pre>
 <pre class="link-defaults">
 type: dfn; spec:css-multicol-1; text:overflow column
+spec:css-pseudo-4; type:selector; text:::first-letter
+spec:css-pseudo-4; type:selector; text:::first-line
 </pre>
 <pre class="anchors">
 url: https://drafts.csswg.org/selectors-3/#subject; type: dfn; text: subject;
@@ -522,8 +525,8 @@ fragment overflow, which also deals with displaying multiple pages.
 
 	<p class="issue">
 		The current implementation of paginated overflow uses
-		the 'overflow'/'overflow-x'/'overflow-y' properties
-		rather than the 'overflow-style' property as proposed
+		the overflow/overflow-x/overflow-y properties
+		rather than the overflow-style property as proposed
 		in the [[CSS3GCPM]] draft
 		(which also matches the [[CSS3-MARQUEE]] proposal).
 		or the 'continue' property as described here.
@@ -770,15 +773,10 @@ the ''continue/fragments'' value of the 'continue' property.
 	<p>
 		Specifying other values of 'display', 'position',
 		or 'float' is permitted, but is not allowed to change
-		the computed value of 'display-inside'.
+		the <a>inner display type</a>.
 		(Since 'continue' only
-		applies to block containers, flex containers, and grid containers
-		the computed value of 'display-inside' is always
-		''display-inside/block'', ''display-inside/flex'', or
-		''display-inside/grid''.
-		<span class="issue">Need to specify exactly how this works,
-		but it depends on
-		having 'display-inside' and 'display-outside' specified.</span>
+		applies to block containers, flex containers, and grid containers).
+		<span class="issue">Need to specify exactly how this works</span>
 	</p>
 
 	<p>
@@ -944,8 +942,8 @@ the ''continue/fragments'' value of the 'continue' property.
 
 	<pre class=propdef>
 		Name: max-lines
-		Value: ''none'' | ''&lt;integer>''
-		Initial: ''none''
+		Value: none | <<integer>>
+		Initial: none
 		Applies to: fragment boxes
 		Inherited: no
 		Animatable: as <a href="https://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
@@ -1027,6 +1025,68 @@ that effect.
 		</td></tr></table>
 	</div>
 
+Privacy and Security Considerations {#priv-sec}
+===============================================
+
+This specification introduces no new security considerations.
+
+The <a href="http://www.w3.org/2001/tag/">TAG</a> has developed a <a href="https://www.w3.org/TR/security-privacy-questionnaire/">self-review questionaire</a>
+to help editors and Working Groups evaluate the risks introduced by their specifications.
+Answers are provided below.
+
+<dl>
+<dt>Does this specification deal with personally-identifiable information?
+<dd>No.
+
+<dt>Does this specification deal with high-value data?
+<dd>No.
+
+<dt>Does this specification introduce new state for an origin that persists across browsing sessions?
+<dd>No.
+
+<dt>Does this specification expose persistent, cross-origin state to the web?
+<dd>No.
+
+<dt>Does this specification expose any other data to an origin that it doesn’t currently have access to?
+<dd>No.
+
+<dt>Does this specification enable new script execution/loading mechanisms?
+<dd>No.
+
+<dt>Does this specification allow an origin access to a user’s location?
+<dd>No.
+
+<dt>Does this specification allow an origin access to sensors on a user’s device?
+<dd>No.
+
+<dt>Does this specification allow an origin access to aspects of a user’s local computing environment?
+<dd>No.
+
+<dt>Does this specification allow an origin access to other devices?
+<dd>No.
+
+<dt>Does this specification allow an origin some measure of control over a user agent’s native UI?
+<dd>No
+
+<dt>Does this specification expose temporary identifiers to the web?
+<dd>No.
+
+<dt>Does this specification distinguish between behavior in first-party and third-party contexts?
+<dd>No.
+
+<dt>How should this specification work in the context of a user agent’s "incognito" mode?
+<dd>No difference in behavior is needed.
+
+<dt>Does this specification persist data to a user’s local device?
+<dd>No.
+
+<dt>Does this specification have a "Security Considerations" and "Privacy Considerations" section?
+<dd>Yes, this is the section you are currently reading.
+
+<dt>Does this specification allow downgrading default security characteristics?
+<dd>No.
+</dl>
+
 <h2 id="changes" class="no-num">
 Changes</h2>
 <h3 id="changes-l3">