w3c
diff --git a/‎css-ui/Overview.bs‎
Lines changed: 55 additions & 10 deletions b/‎css-ui/Overview.bs‎
Lines changed: 55 additions & 10 deletions
@@ -96,6 +96,10 @@ dynamic presentation related features in HTML.
 user interfaces which make use of a directional navigation model.
 </ul>
 
+<div>
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-48">Open issue #50</a> related to purpose and scope: there has been a request to re-add the <css>user-select</css> property back to CSS3-UI with the claim that there are three implementations for one or more of the previously specified values for the property. The proposed resolution is stick with defering <css>user-select</css> to CSS UI Level 4 because there is too much interop to figure out. That said, this property is at risk of being re-added.
+</div>
+
 <h2 id="interaction">Module Interactions</h2>
 
 This document defines new features not present in earlier specifications.
@@ -250,6 +254,8 @@ demonstration of sample CSS and HTML:
 
 Note: The ''padding-box'' value is at risk.
 
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-69">Open issue 69</a>: box-sizing insufficiently specified for replaced elements.
+
 <h2 id="outline-props">Outline properties</h2>
 
 At times, style sheet authors may want to create outlines around
@@ -267,6 +273,12 @@ The outline properties control the style of these dynamic outlines.
 
 Keyboard users depend on outline on elements in the :focus state for interaction with the page, thus authors must not make the outline invisible on such elements without making sure an alternative highlighting mechanism is provided.
 
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-51">Open issue 51</a>: Applying transforms to outlines behaves strangely in current implementations (See <a href="
+http://florian.rivoal.net/csswg/outline.html">transformed outline test case</a>). Proposed resolution: leave transformed outline rendering undefined in CSS3-UI.
+
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-54">Open issue 54</a>: Outline rendering is under-specified, and details are not interoperable (See <a href="https://lists.w3.org/Archives/Public/www-style/2014Dec/0134.html">a few outline rendering test cases</a>). Tentative proposal: leave non-interop details unspecified in CSS3-UI, attempt to converge in level 4.
+
+
 <h3 id="outline">'outline' property</h3>
 
 <table class="propdef"><tbody>
@@ -544,31 +556,36 @@ The 'resize' property applies to elements
 whose computed 'overflow' value
 is something other than ''visible''.
 
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-52">Open issue 52</a>: Implementation handling of 'resize' on ::before generated content is buggy and not interoperable (See: <a href="http://dabblet.com/gist/ab432c3f6a8f672cd077">resize on :before test case</a>). A few possible resolutions: explicitly specify :resize does not apply to generated content (result undefined), (result no effect - would be at risk) or that it does apply (not interop, would be at risk).
+
 When an element is resized by the user,
-the user agent keeps track of a resize factor
-(which is initially 1.0) for the width and height,
-which it then applies to the computed width and height
+the user agent uses a resize function
+based on the unresized computed width and height
 as part of determining the used width and height.
 The element's contents (and surroundings) are reformatted as necessary.
 
-The resize factor introduces a step in width/height calculations and formatting
+The resize function introduces a step in width/height calculations and formatting
 as described in <a href="http://www.w3.org/TR/CSS21/visudet.html">chapter 10 of CSS2.1</a>.
 Specifically the following step is inserted between steps 1 and 2
 of the algorithm in <a href="http://www.w3.org/TR/CSS21/visudet.html#min-max-widths">section 10.4</a>
 and <a href="http://www.w3.org/TR/CSS21/visudet.html#min-max-heights">10.7</a> in CSS2.1 [[!CSS21]],
 where [dimension] is 'width' for 10.4 and 'height' for 10.7.
-1b. If the resize [dimension] factor is not 1.0,
- then the tentative used [dimension] is multiplied by that factor,
+1b. If the resize [dimension] function is in use,
+ then the tentative used [dimension] is computed with that function,
  and the rules above are applied again,
- but this time using the result of that multiplication as the computed value for '[dimension]'.
+ but this time using the result of that function as the computed value for '[dimension]'.
 </blockquote>
 
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-47">Open issue 47</a>: There is evidence that implementations support resize by setting inline style width and height on the element, and there is <a href="http://lists.w3.org/Archives/Public/www-style/2014Dec/0177.html">a proposal to specify that behavior explicitly</a> (<a href="https://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html">previous proposal</a>).
+
 With regard to interactivity and the Document Object Model (DOM),
-the resize factor on an element lasts the lifetime of the element,
-however, if the 'resize' property itself is altered
+the resize function on an element lasts the lifetime of the element,
+however, if the computed 'resize' property itself is altered
 (e.g. via pseudo-class change or via DOM manipulation),
-then the resize factor is reset to 1.0.
+then the resize function is reset to 
+using the element's unresized computed width and height.
+
 
 The precise direction of resizing
 (i.e. altering the top left of the element or altering the bottom right)
@@ -579,10 +596,13 @@ and 'bottom' properties,
 whether the language of the element is right-to-left etc.
 The precise direction of resizing is left to the UA to properly determine for the platform.
 
+The user agent should allow the user to resize the element with no other constraints than what is imposed by min-width and max-width (at risk due since <a href="http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html">only Firefox currently supports this</a>. Related: <a href="https://wiki.csswg.org/spec/css3-ui#issue-53">Issue 53</a>).
+
 The user agent may restrict the resizing range to something suitable,
 such as between the original formatted size of the element,
 and large enough to encompass all the element's contents.
 
+
 <div class="example"><p style="display:none">Example(s):
 
 For example,
@@ -645,6 +665,10 @@ its line box edge
 in the inline progression direction of its block container element ("the block")
 that has 'overflow'
 other than ''visible''.
+
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-68">Open issue 68</a>: Should text-overflow apply even when overflow is visible? Possible resolutions: Appl
93CC
y text-overflow regardless of overflow, or consider reverting 
+<a href="https://www.w3.org/wiki/CSS3-UI#Issue_32">resolved issue 32</a>.
+
 Text can overflow for example when it is prevented from wrapping
 (e.g. due to '<code class="lang-css">white-space: nowrap</code>'
 or a single word is too long to fit).
@@ -703,6 +727,8 @@ atomic inline-level element</a>
 on a line
 must be clipped rather than ellipsed.
 
+Implementations may ellipse at a text wrap opportunity that occurs before a character boundary where an ellipsis is required.
+
 <h4 id="ellipsing-details" class="no-num no-toc">ellipsing details</h4>
 <ul>
 <li>
@@ -975,6 +1001,14 @@ The <a>default object size</a> for cursor images is
 a UA-defined size that should be based on
 the size of a typical cursor on the UA's operating system.
 
+The <a>concrete object size</a> is determined using 
+the <a>default sizing algorithm</a>. 
+If an operating system is 
+<strong>incapable</strong> of rendering a cursor above a given size, 
+cursors larger than that size must be shrunk to within
+the OS-supported size bounds, 
+while maintaining the cursor image's intrinsic ratio, if any.
+
 The optional &lt;x&gt; and &lt;y&gt; coordinates
 identify the exact position within the image which is the pointer position (i.e., the hotspot).
 </dd>
@@ -1000,11 +1034,18 @@ they must be clamped (independently) to fit.
 </dl>
 
 general purpose cursors
+
 <dl>
 <dt style="cursor:auto">auto</dt>
 <dd>The UA determines the cursor to display based on the current
 context.
+
+<div>
+<a href="https://wiki.csswg.org/spec/css3-ui#issue-48">Open issue #48</a>: There are reports that this description of cursor: auto is insufficient and not interoperable. Current plan: restrict the auto value to handling things that cannot be described by the UA stylesheet, pending detailed proposal, likely based on <a href="https://lists.w3.org/Archives/Public/www-style/2013Jan/0275.html">David Baron's proposal</a>.
+</div>
+
 </dd>
+
 <dt style="cursor:default">default</dt>
 <dd>The platform-dependent default cursor. Often rendered as an arrow.
 </dd>
@@ -1352,6 +1393,8 @@ This specification deliberately does not attempt to document the functionality o
 
 <h2 class="no-num" id="acknowledgments">Appendix A. Acknowledgments</h2>
 
+This appendix needs to be updated with acknowledgements from input, feedback, and contributions from 2012-01-17 to the present!
+
 This appendix is <em>informative</em>.
 
 Thanks to feedback and contributions from
@@ -1380,6 +1423,8 @@ and Domel.
 
 <h2 class="no-num" id="changes">Appendix B. Changes</h2>
 
+This appendix needs to be updated with changes from 2012-01-17 to the present!
+
 This appendix is <em>informative</em>.
 
 In general this draft contains numerous