Draft:    http://www.w3.org/TR/2015/WD-css3-ui-20150519/
Title:    CSS Basic User Interface Module Level 3 (CSS3 UI)

----
Issue 1.
Summary: css3-ui should have a test suite
From: Tantek Çelik
Resolved: LCWD has link to Test suite
Closed: Accepted

----
Issue 2.
Summary: Change name/title of spec to be consistent with other CSS3 modules
From: Tantek Çelik
Resolved: Editorial
Closed: Accepted

----
Issue 3.
Summary: ::value needs to specify which properties are allowed on that pseudo-element
From: Tab Atkins
Comment: http://lists.w3.org/Archives/Public/www-style/2010Mar/0158.html
Resolved: Specify the same properties that apply to ::first-line
Closed: Accepted
Note: Later made irrelevant since ::value was dropped

----
Issue 4.
Summary: computed value of 'pointer-events' vs initial value vs SVG vs CSS3-UI conflict.
A quick test shows that IE9 and Opera return 'visiblePainted', while WebKit and Firefox return 'auto'.
From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 5.
Summary: In SVG 1.1 the 'pointer-events' property only applies to 'graphics elements',
but in css3-ui it applies to all elements. Why?
From: Erik Dahlstrom, Kevin Ar18
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0268.html
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0304.html
Comment: http://www.w3.org/2010/09/27-fx-minutes.html#item03
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 6.
Summary: Normatively reference SVG 1.1 for 'fill' and 'stroke' property definitions.
From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 7.
Summary: The note about how 'fill' and 'stroke' don't affect the result for 'all' is missing
Compare with the SVG 1.1 pointer-events definition:
http://www.w3.org/TR/SVG11/interact.html#PointerEventsProperty

From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 8.
Summary: pointer-events definition lacks many of the details from the SVG 1.1 specification
http://www.w3.org/TR/SVG11/interact.html#PointerEventsProperty,
e.g how 'clip-path' and 'mask' affects pointer-events, how text elements are handled etc.
From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 9.
Summary: How opacity (and other forms of alpha, e.g rgba, fill-opacity, stroke-opacity etc) affects 'pointer-events' is undefined.
From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 10.
Summary: How 'clip-path', 'mask' and 'filter' affect 'pointer-events' is undefined.
From: Erik Dahlstrom
Comment: http://lists.w3.org/Archives/Public/www-style/2010Sep/0818.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 11.
Summary: multiple issues from Kevin Ar18 2010-11-17
From: Kevin Ar18
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0257.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 12.
Summary: what are effects of 'pointer-events' with regards to keyboard navigation?
From: Doug Schepers
Comment: http://lists.w3.org/Archives/Public/public-fx/2010OctDec/0106.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 13.
Summary: should CSS3 UI (or some future version) incorporate a 'focusable' property (like in SVG)
From: Tantek Çelik
Closed: Deferred
Note: To be specified in CSS UI Level 4
Verified: Reporter is spec editor

----
Issue 14.
Summary: example for 'appearance' values 'pop-up-menu' and 'radio-group' and 'list-menu'
should use same content to illustrate different visualizations for same semantics.
From: Charles Belov
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0189.html
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jan/0224.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 15.
Summary: add second 'list-menu' example that shows multiselect behavior and use same content as 'checkbox-group'
From: Charles Belov
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0189.html
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jan/0224.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 16.
Summary: What happens if a semantic single-select element is styled as appearance 'checkbox-group'?
From: Charles Belov
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0189.html
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jan/0224.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 17.
Summary: What happens if a semantic multi-select element is styled as appearance 'radio-group' or 'pop-up-menu'?
From: Charles Belov
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0189.html
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jan/0224.html
Closed: Deferred
Note: Pertains to a feature that was removed from css-ui level 3, potentially to be included in level 4

----
Issue 18.
Summary: How does text-overflow:ellipsis work with overflow-style: marquee-line?
From: Andrew Fedoniouk
Comment: http://lists.w3.org/Archives/Public/www-style/2008Dec/0109.html
Comment: http://www.w3.org/TR/2008/CR-css3-marquee-20081205/#overflow-style
Closed: OutOfScope

Note: CSS3 Marquee has been retired, as nobody implemented it
and the WG does not encourage anyone to.
This clarification is therefore not longer needed,
and has been removed from the draft, along with all references to CSS3 Marquee

----
Issue 19.
Summary: CSS3-UI should define 'overflow-x' and 'overflow-y' properties
From: David Hyatt / Tantek Çelik
Comment: http://lists.w3.org/Archives/Public/www-style/2010Nov/0049.html
Resolved: Defer to http://dev.w3.org/csswg/css-overflow/
Closed: Deferred

----
Issue 20.
Summary: text-overflow definition is ambiguous as to whether it applies to vertical overflow of text
From: Alan Hogan in private email to Tantek Çelik
; URL : http://dev.w3.org/csswg/css3-ui/#text-overflow0
; URL : http://dl.dropbox.com/u/105727/web/text-wrap-ellipsis.html
Resolved: Bugfix
Closed: Accepted

Note: No one has implemented text-overflow
for anything other than inline progress.
Therefore we explicitly clarify this deatil.

----
Issue 21.
Summary: text-overflow definition must include <string> value and 2 values option,
but with both explicitly at-risk.

From: CSS WG
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html
Resolved: http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html
Closed: Accepted

----
Issue 22.
Summary: How should text selection behave in the presence of a text-overflow ellipsis?
From: Tantek Çelik
Comment: http://www.w3.org/Style/CSS/Tracker/issues/279
Resolved: http://lists.w3.org/Archives/Public/www-style/2012Nov/0263.html
Closed: Accepted

----
Issue 23.
Summary: Update CSS IS AWESOME example to show non-ellipsed last line.
From: Rossen
Comment: http://lists.w3.org/Archives/Public/www-style/2012Nov/0263.html
Resolved : Editorial (RESOLVED at 2012-10-30 TPAC CSSWG f2f meeting)
Closed: Accepted

----
Issue 24.
Summary: Provide horizontal scrolling text-overflow example revealing more text that is elided
From: Tantek Çelik
Comment: http://lists.w3.org/Archives/Public/www-style/2009Nov/0219.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0321.html
Resolved: Editorial
Closed: Accepted
Note: Was blocked by ambiguity in the spec, tracked as Issue 59, now resolved.

----
Issue 25.
Summary: nav-index property is not well implemented, nor expected to be.
Also, is problematic (per similar issues on tabindex in HTML).

From: Tantek Çelik
Comment: http://lists.w3.org/Archives/Public/www-style/2012Oct/thread.html#msg468
Comment: http://lists.w3.org/Archives/Public/www-style/2011Nov/0712.html
Comment: http://lists.w3.org/Archives/Public/www-style/2011Nov/thread.html#msg440 (continues following month)
Comment: http://lists.w3.org/Archives/Public/www-style/2011Nov/thread.html#msg441 (continues following month)
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0295.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2014Nov/0401.html
Closed: Deferred
Verified: Reporter is spec editor

----
Issue 26.
Summary: add 'cursor' values 'grab' and 'grabbing' per existing interop
support by Gecko and -webkit- prefixed in WebKit
From: Frank Yan / Tantek Çelik
Comment: http://lists.w3.org/Archives/Public/www-style/2013Apr/0058.html
Resolved: http://lists.w3.org/Archives/Public/www-style/2013Apr/0428.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0319.html
Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=880672
Closed: Accepted

----
Issue 27.
Summary: Specify that 'cursor' propagates from the root to the viewport
From: Tab Atkins
Comment: http://krijnhoetmer.nl/irc-logs/whatwg/20130523#l-684
Comment: http://lists.w3.org/Archives/Public/www-style/2013May/0301.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0300.html
Resolved: Propagates from the root element to the viewport
Closed: Accepted

----
Issue 28.
Summary: link to nav-* directional navigation tests from nav-* section, and in tests section in header
From: Tantek Çelik
Comment: http://lists.w3.org/Archives/Public/www-style/2013Nov/0271.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0299.html
Comment: https://github.com/w3c/csswg-test/pull/372
Resolved: Tests have been added to the test suite already,
which is linked from the spec.

Closed: Accepted

----
Issue 29.
Summary: nav-* directional navigation properties definition prose fixes
From: Simon Sapin
Comment: http://lists.w3.org/Archives/Public/www-style/2013Oct/0102.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0298.html
Reslolved: Editorial
Closed: Accepted

----
Issue 30.
Summary: Re-add ::selection, define according to existing impl interop of ::selection
From: Tantek Çelik
Comment: http://www.w3.org/2013/12/11-css-irc#T18-01-59
Comment: http://lists.w3.org/Archives/Public/www-style/2008Oct/0268.html
 (list of questions/issues with ::selection)
Comment: http://lists.w3.org/Archives/Public/www-style/2013Dec/0240.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/thread.html#msg188
Resolved: http://www.w3.org/mid/CADhPm3vmeGC6ALFor-98+E8sa2EufvgcNGvGO0WAxjx7r75GzA@mail.gmail.com
Closed: Deferred
Verified: http://www.w3.org/mid/CADhPm3s4ZmQJVgJu3pAnnHH6Q0SU3B+t5MBkLhggfD7-J=xuqg@mail.gmail.com

----
Issue 31.
Summary: add 'caret-color' property at risk to css3-ui
From: Andrey Rybka (Bloomberg) <arybka@bloomberg.net>
Comment: http://lists.w3.org/Archives/Public/www-style/2011Nov/0772.html (Initial proposal)
Comment: http://lists.w3.org/Archives/Public/www-style/2014Aug/0236.html
Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1063162 (Gecko intent)
Comment: http://lists.w3.org/Archives/Public/www-style/2014Sep/0172.html
Resolved: http://lists.w3.org/Archives/Public/www-style/2014Oct/0260.html
Closed: Accepted

----
Issue 32.
Summary: use line box edge instead of block container edge for the purpose of determining text-overflow
From: David Baron
Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=944200#c3
Response: http://lists.w3.org/Archives/Public/www-style/2014Feb/0140.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Feb/0141.html (Tab says reasonable)
Comment: https://bugs.webkit.org/show_bug.cgi?id=115746
Resolved: Change the opening sentence of text-overflow section
from "overflows its block container element" to "overflows its line box edge",
and any other similar references to block container edge to line box edge.

Closed: Accepted
Note: Effective consensus from Webkit (per their fix of 115746),
Chrome (Tab's email), and Gecko (per 944200 discussion).

----
Issue 33.
Summary: In the description of the <target-name> parameter of the nav-*
properties, the word string should be replaced by <string>
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0708.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0442.html
Resolved: Editorial
Closed: Accepted

----
Issue 34.
Summary: The text-overflow property definition uses () for grouping, but we should use []
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0808.html
Resolved: Editorial
Closed: Accepted

----
Issue 35.
Summary: Editorial: distinguishing public web sites from web applications is non obvious
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0808.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Dec/0072.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Jan/0581.html
Resolved: The entire feature is being dropped, comment no longer relevant
Closed: OutOfScope

----
Issue 36.
Summary: "Content" properties for several input elements are locale specific
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0808.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0444.html
Resolved: Editorial
Closed: Accepted

----
Issue 37.
Summary: spec differs from implementations
regarding whether resize only applies in 1 dimension
if overflow-x or -y is visible in one of the dimensions.

From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0713.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0445.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2014Nov/0553.html
Closed: Accepted

----
Issue 38.
Summary: what to do if outline-offset is negative, especially to the point
that the offset is more than half the element size or similar values that make
it impossible to draw?
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0601.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0449.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Dec/0033.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Jan/0581.html
Closed: Accepted

----
Issue 39.
Summary: Various issues with ime-mode
From: Kang-Hao (Kenny) Lu <kennyluck@csail.mit.edu>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0759.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0072.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Jan/0581.html
Resolved: The entire feature is being dropped, comments no longer relevant
Closed: OutOfScope

----
Issue 40.
Summary: ime-mode is windows specific and bad design, and should not be
standardized. (has replacement suggestion)
From: Masayuki Nakano <masayuki@d-toybox.com> and James Craig <jcraig@apple.com>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/0959.html
 (Gecko ime-mode implementer saying should not be standardized)
Comment: http://lists.w3.org/Archives/Public/www-style/2013May/0075.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Dec/0072.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0090.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Jan/0581.html
Closed: Accepted

----
Issue 41.
Summary: The 'inherit' value is globally defined for all properties,
and the preferred style appears to be to omit it in property definitions.
From: Tab Atkins
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jul/0202.html
Resolved: Editorial
Closed: Accepted

----
Issue 42.
Summary: drop “inverted” from outline-color, webkit and gecko don’t do it
From: Tab Atkins
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jul/0202.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0493.html
Resolved: http://lists.w3.org/Archives/Public/www-style/2014Dec/0067.html
Closed: Rejected
Note: Kept normative text the same as the behavior is optional,
but made editorial improvements clarifying what non-supporting UAs should do.

Verified: Reporter is CSSWG member present when resolving

----
Issue 43.
Summary: Add note or author conformance requirement
to not make outlines invisible on focusable elements,
for accessibility reasons

From: Michael Cooper <cooper@w3.org>
Comment: http://lists.w3.org/Archives/Public/www-style/2012Feb/1213.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0494.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2014Dec/0067.html
Closed: Accepted

----
Issue 44.
Summary: use <image> instead <uri> in the cursor property,
like http://www.w3.org/TR/css3-background/#value-types.
Allows high res images with image-set, gradients…

From: Fantasai (responding to Tab Atkins) and Rick Byers
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jul/0202.html
Comment: http://lists.w3.org/Archives/Public/www-style/2012Jul/0140.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0496.html
Resolved: http://lists.w3.org/Archives/Public/www-style/2014Dec/0067.html
Closed: Accepted

----
Issue 45.
Summary: include an example highlighting the <target> part of the nav-* syntax. Suggestion: nav-up: #foo "bar"
From: Yves Lafon
Comment: http://lists.w3.org/Archives/Public/www-style/2012Oct/0499.html
Resolved: Editorial
Closed: Accepted

----
Issue 46.
Summary: what happens if <x> and <y> are out of bounds for the cursor property
From: Kang-Hao (Kenny) Lu and Tab Atkins
Comment:  http://lists.w3.org/Archives/Public/www-style/2012Feb/0712.html
Comment: http://lists.w3.org/Archives/Public/www-style/2012Nov/0331.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0501.html
Resolved: Clamp, independently.
Closed: Accepted

----
Issue 47.
Summary: The specced 'resize' property's behavior is *completely* different
from the behavior implemented in browsers supporting the property

From: François Remy
Comment: http://lists.w3.org/Archives/Public/www-style/2012Dec/0221.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0177.html
Response: https://lists.w3.org/Archives/Public/www-style/2015Feb/0149.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Mar/0314.html
Closed: Accepted

----
Issue 48.
Summary: description of cursor: auto insufficient and not interoperable
From: David Baron
Comment: http://lists.w3.org/Archives/Public/www-style/2013Jan/0275.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0531.html
Response: https://lists.w3.org/Archives/Public/www-style/2015Feb/0039.html
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0182.html
 (issues, and previous in this thread too)
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Mar/0314.html
Closed: Accepted

----
Issue 49.
Summary: there is no interop between UAs about showing tooltips of the ellipsed text
From: Philip Walton
Comment: http://lists.w3.org/Archives/Public/www-style/2013Apr/0013.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0532.html
Resolved: http://www.w3.org/mid/CADhPm3vR=hZWgbq8xrCsxR4YhKnFzi0gEzR-3pa7s_tToY62ig@mail.gmail.com
Response: http://lists.w3.org/Archives/Public/www-style/2014Dec/0061.html
Closed: Rejected

----
Issue 50.
Summary: Add user-select back to css-ui, it has 3 implementations
From: Tab Atkins and Theresa O'Connor
Comment: http://lists.w3.org/Archives/Public/www-style/2013Apr/0537.html
Comment: http://lists.w3.org/Archives/Public/www-style/2012Jul/0541.html
Response: http://lists.w3.org/Archives/Public/www-style/2014Nov/0536.html
Response: http://www.w3.org/mid/C05EA97A-11FE-42A4-85CC-0D69566E21DF@rivoal.net
Resolved: http://www.w3.org/mid/CAEV2_WbUW=Et8PZreXbi1oNruE3ekF8=yETbkogXtvojvUa_=A@mail.gmail.com
Closed: Deferred
Verified: http://www.w3.org/mid/CAAWBYDBMdN5fjvuCeYY+q-jg4dh2Rubmcnu7Ucj=mGOozVp6+A@mail.gmail.com
Note: Added to level 4 http://dev.w3.org/csswg/css-ui-4/#content-selection

----
Issue 51.
Summary: applying transforms to the outline is weird, especially in 3d.
From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2013Aug/0423.html
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0134.html
Comment: http://florian.rivoal.net/csswg/outline.html
 (test case that demonstrates applying transforms to outlines behaving strangely)
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Mar/0314.html
Closed: Deferred
Verified: Reporter is spec editor

----
Issue 52.
Summary: behavior of resize on pseudo-elements buggy and ambiguously defined
From: Lea Verou
Comment: http://lists.w3.org/Archives/Public/www-style/2014Jul/0477.html
Comment: http://dabblet.com/gist/ab432c3f6a8f672cd077
 (test case demonstrating non-interop / buggy behavior)
Resolved: http://www.w3.org/mid/CADhPm3vN8CwXDRM1N=9Pf8f1f906xwp2t6CfTjBYu=y_oV+v8Q@mail.gmail.com
Closed: Accepted

----
Issue 53.
Summary: resize factor behavior is weird when width / height are later dynamically modified
From: Lea Verou
Comment: http://lists.w3.org/Archives/Public/www-style/2014Jul/0517.html
; URL : http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html
Resolved: Add proposed text from 0063.html, "allows the user to
resize the element with no other constraints than what is imposed by min-width
and max-width" - note at risk since FF only, link to 0063.html email with
analysis.
Closed: Accepted

----
Issue 54.
Summary: Can text-overflow ellipsis not break in the middle of a word?
From: Stuart Langridge
Comment: https://twitter.com/sil/status/537627213789949952
Closed: Accepted
Resolved: Add to spec "Implementations may ellipse at a text wrap opportunity instead of a character boundary."
Note: Later overturned, per issue 76.

----
Issue 55.
Summary: Outline has a very loose definition, and significant interop problems. Should we tighten it up?
From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0134.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Mar/0314.html
Closed: Deferred
Verified: Reporter is spec editor

----
Issue 56.
Summary: WG resolved to make outline corners rounded to match borders,
but it was only lightly discussed, and not obvious how that should work

From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0145.html
Resolved: "To the extent that the outline follows the border edge,
it should follow the border-radius curve"

Closed: Accepted

----
Issue 57.
Summary: the default object size for cursors is defined in CSS2.1,
but not in CSS3-UI, which replaces it

From: Tab Atkins
Comment: http://lists.w3.org/Archives/Public/www-style/2010Dec/0080.html
Resolved: Bugfix
Closed: Accepted

----
Issue 58.
Summary: border box is a well defined term. Let's use it.
From: Fantasai
Comment: http://www.w3.org/mid/4BF38810.2060005@inkedblade.net
Resolved: Bugfix
Closed: Accepted

----
Issue 59.
Summary: Spec is ambiguous as to what happens
when the start of the line overflows
with a single value used on text-overflow

From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0321.html (see point #2)
Comment: http://lists.w3.org/Archives/Public/www-style/2011Sep/0504.html (webcompat single value end only)
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0342.html (Gecko preference in agreement)
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0346.html (Google pref in agreement)
Resolved: clear ambiguity to say that single value only causes ellipsis at the end line edge.
Closed: Accepted

----
Issue 60.
Summary: Information about when the resize factor gets reset is not sufficiently specific
From: Boris Zbarsky
Comment: http://lists.w3.org/Archives/Public/www-style/2004May/0222.html
Resolved: Bugfix
Closed: Accepted

----
Issue 61.
Summary: Cross reference should be updated to css3-background instead of css2.1
From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0263.html
Resolved: Editorial
Closed: Accepted

----
Issue 62.
Summary: Overview is redundant with Introduction, and introduction contains out of date sentence.
From: Florian
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0434.html
Resloved: Editorial
Closed: Accepted

----
Issue 63.
Summary: Section "Dependencies on other modules" is redundant with bibliography,
but normative "Module interactions" section defining what the spec replaces is missing

From: Florian
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0433.html
Resolved: Editorial
Closed: Accepted

----
Issue 64.
Summary: Drop the icon property and the icon value of the content property,
they are not implemented.

From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0230.html
Closed: Accepted

----
Issue 65.
Summary: Drop the XForms related pseudo-elements
From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0229.html
Closed: Accepted

Note: kept ::value and ::choices because they apply to HTML (especially HTML5),
and https://bugzilla.mozilla.org/show_bug.cgi?id=648643 Mozilla has an open bug
to implement them. Later removed by Issue 71.

----
Issue 66.
Summary: Drop the pseudo-classes, they have a more up to date definition in selectors 4
From: Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0228.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2014Nov/0401.html
Closed: Accepted

----
Issue 67.
Summary: Editorial improvement to clarify where the outline is
From: Axel Dahmen
Comment: http://lists.w3.org/Archives/Public/www-style/2014Dec/0104.html
Resolved: Editorial
Closed: Accepted

----
Issue 68.
Summary: apply text-overflow even when overflow is visible?
From: Mats Palmgren, Florian Rivoal
Comment: http://lists.w3.org/Archives/Public/www-style/2014Nov/0425.html
Comment: http://lists.w3.org/Archives/Public/www-style/2015Jan/0048.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Mar/0314.html
Closed: Rejected
Verified: Florian is spec Editor, Mats is from Mozilla who was represented during discussion

----
Issue 69.
Summary: box-sizing insufficiently specified for replaced elements
From: Boris Zbarsky
Comment: http://lists.w3.org/Archives/Public/www-style/2011Jul/0232.html
Comment: https://lists.w3.org/Archives/Public/www-style/2011Jul/att-0232/test.html
 (test case from Boris, 100px intrinsic size, max-height 100, borders 40 + 40)
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0243.html
 (two test pages, 3 tests each with/without box-sizing of SVG embedded images with intrinsic width and/or ratio.)
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0245.html
 (box-sizing test with different border-width and max-height values)
Response: https://lists.w3.org/Archives/Public/www-style/2015Feb/0445.html
Resolution: https://lists.w3.org/Archives/Public/www-style/2015Apr/0144.html
Closed: Accepted

----
Issue 70.
Summary: CSS3-UI defines the 'default object size' for cursors,
but not the 'concrete object size'

From: Tab Atkins
Comment: http://lists.w3.org/Archives/Public/www-style/2015Jan/0163.html
Resolved: Bugfix
Closed: Accepted

----
Issue 71.
Summary: WG resolved to drop all XForms related pseudo elements from CSS-UI,
but ::value and ::choices were retained,
as they apply to HTML in addition to XForms as they were initially specified for.
However, they are not implemented anywhere,
and it is not clear that they effectively solve the problem they were introduced for.

From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2014Nov/0401.html
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jan/0046.html
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jan/0280.html
Closed: Accepted

----
Issue 72.
Summary: All browsers should be treated equally with regards to obsoleting the 'ime-mode' property,
instead of saying "must not add support" for those that don't have it
but "should drop support" for those that do.
From: David Baron (in telcon)
Comment: http://www.w3.org/mid/CADhPm3uJkugzOcz-vaKXkFMGik=R2AXwxLmXaFtUj3E_HRnsyA@mail.gmail.com
Comment: http://krijnhoetmer.nl/irc-logs/css/20150128#l-605
Resolved: Bugfix
Closed: Accepted

----
Issue 73.
Summary: Support for negative outline-offset is marked as optional and at-risk.
However, all browsers that support outline-offset support negative values.
The only issue was the lack of interop for large negative values.
The new spec prose introduced to define interoperable behavior is fine.

From: Florian Rivoal
Comment: http://www.w3.org/mid/CADhPm3uJkugzOcz-vaKXkFMGik=R2AXwxLmXaFtUj3E_HRnsyA@mail.gmail.com
Resolved: Reduce scope of "at-risk"
Closed: Accepted

----
Issue 74.
Summary: The phrasing of what happens with large negative values
in the outline-offset property is unclear,
and makes it sound like we should keep a blank space
of outline-width * 2 inside the outline at minimum.

From: Fantasai
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jan/0581.html
Resolved: Clarify that outline-width * 2 is the outside dimension of the shape, wording up to editor.
Closed: Accepted

----
Issue 75.
Summary: As we mark ime-mode as obsolete, we should point readers of the
spec to the alternative ways to address the issue that ime-mode was attempting
to solve.
From: Florian Rivoal
Comment: http://logs.csswg.org/irc.w3.org/css/2015-01-28/#e513809
Resolved: Editorial
Closed: Accepted

----
Issue 76.
Summary: the change introduced to address [[#Issue 54]] causes problems with bidi,
scrolling, and is not necessarily an improvement anyway
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0007.html
Resolved: http://www.w3.org/mid/CADhPm3vN8CwXDRM1N=9Pf8f1f906xwp2t6CfTjBYu=y_oV+v8Q@mail.gmail.com
Closed: Accepted
Note: Reverts resolution Issue 54.

----
Issue 77.
Summary: text-overflow: clip should not clip at the end of the line box
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0342.html
Resolved: Bugfix
Closed: Accepted

----
Issue 78.
Summary: Clarify that the :focus pseudo class matches
when the focus is move to an element using the directional navigation properties,
even if that element cannot otherwise be focused.
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0344.html
Resolved: http://www.w3.org/mid/CADhPm3s8NnMe1v6f4GY02xoBbTs9f_oo133knvn94tEZVx_oWw@mail.gmail.com
Closed: Accepted

----
Issue 79.
Summary: CSS3-UI "does not define" stacking behavior of outlines,
but CSS2.1 and css-position do. Clarify.
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0357.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Feb/0494.html
Closed: Accepted

----
Issue 80.
Summary: "Should drop ime-mode ASAP" is too strong as long as a better alternative has not been standardised
From: Masayuki Nakano
Comment: https://lists.w3.org/Archives/Public/www-style/2015Feb/0530.html
Closed: Accepted
Note: Duplicate. Group already resolved to drop "should drop" as part of issue 72 (and issue 40 updated) resolution.

----
Issue 81.
Summary: A few (mostly editorial) tweaks to the definition of the resize property
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0051.html
Closed: Accepted
Resolved: Editorial
Note: Part of this issue split into Issue 101.

----
Issue 82.
Summary: Drop the note and the at-risk mention about the "block container" aspect of the clip value,
since it is the historic behavior implemented by everybody
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0053.html
Resolved: Bugfix
Closed: Accepted

----
Issue 83.
Summary: A couple of editorial tweaks to the definition of the resize property
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0053.html
Resolved: Editorial
Closed: Accepted

----
Issue 84.
Summary: no file format required by the spec for cursor
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0199.html
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0217.html
Resolved: http://www.w3.org/mid/CADhPm3urfwvGe0-h0pbE6GtB5isYGsMNnrC36zh-j8xUrL=hmQ@mail.gmail.com
Closed: Accepted

----
Issue 85.
Summary: Tiny leftover of nav-index removal should be erased
From: Florian Rivoal
Comment: http://www.w3.org/mid/D34E1BE4-AAF8-4229-B137-3D156BE9DA0C@rivoal.net
Resolved: Editorial
Closed: Accepted

----
Issue 86.
Summary: caret-color should be inherited, and auto should compute to auto
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0197.html
Resolved: Bugfix
Closed: Accepted

----
Issue 87.
Summary: define what happens if a target-name starting with an "_" is
provided
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0196.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Apr/0320.html
Closed: Accepted

----
Issue 88.
Summary: incorrect prose (rtl issue) in in text-overflow
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0195.html
Resloved: Bugfix
Closed: Accepted

----
Issue 89.
Summary: The precise direction of resizing is *not* left to the UA
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0194.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Apr/0332.html
Closed: Accepted

----
Issue 90.
Summary: "the cursor’s coordinate system" is insufficiently defined for various <image> values
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0193.html
Resolved: http://www.w3.org/mid/CADhPm3vodAs3xAZrT4Of1s6GX6GfkaYdjLY-teYTN4iw=G8jmw@mail.gmail.com
Closed: Accepted
Note: The substantive edits are deferred to css-images

----
Issue 91.
Summary: A few minor tweaks (editorial) to css-ui
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0192.html
Resolved: Editorial
Closed: Accepted

----
Issue 92.
Summary: In vertical text with text-orientation upright,
U+2026 does not seem to be the best character for the ellipsis
From: Xidorn Xuan
Comment: http://www.w3.org/mid/CAMdq69_N1aGTswQM7807xoZSK4berTsqq5H-cg07AmbgBPjUFA@mail.gmail.com
Response: http://www.w3.org/mid/465B66C2-E8B1-4ED4-9020-79B16DB40E43@rivoal.net
Resolved: http://www.w3.org/mid/CADhPm3vodAs3xAZrT4Of1s6GX6GfkaYdjLY-teYTN4iw=G8jmw@mail.gmail.com
Closed: Accepted

----
Issue 93.
Summary: "cursor: default" collides with the css-wide "default" value defined in css-cascade-4
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Apr/0329.html
Resolved: http://www.w3.org/mid/CADhPm3sAMNBxd2+EzebRA10Ow23YXL34MdKH3KRP_1wO3uBwAQ@mail.gmail.com
Closed: Accepted
Note: naming conflic to be resolved by changing css-cascade-4

----
Issue 94.
Summary: The default stylesheet for HTML should have "resize: both" for <textarea>
From: Timeless
Comment: http://www.w3.org/mid/CACsW8eGS3kZQ8a3jPAgrDaXW1WVmUQLo5vYzYty991JZzxMVdw@mail.gmail.com
Resolved: http://www.w3.org/mid/CADhPm3u6uDnhLZa3157EUi1GKKMFx-wF9GVOe7zAktbAGX5E7Q@mail.gmail.com
Closed: Accepted

----
Issue 95.
Summary: "Ellipsed" isn't in the dictionary, use "Ellipsized" instead
From: Timeless
Comment: http://www.w3.org/mid/CACsW8eGS3kZQ8a3jPAgrDaXW1WVmUQLo5vYzYty991JZzxMVdw@mail.gmail.com
Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html
Resolved: Editors' discretion
Closed: Rejected
Verified: https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html
Note: 2015-06-10 WG telcon resolved to reject. Such editorial wording is up to editors.

----
Issue 96.
Summary: Clarify the at-risk section
From: timeless
Comment: http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com
Resolved: Editorial
Closed: Accepted

----
Issue 97.
Summary: Make stronger statement regarding authors disabling the outline on :focus
From: timeless
Comment: http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com
Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html
Resolved: Editorial
Closed: Accepted
Note: Part of this issue split into Issue 102.

----
Issue 98.
Summary: Add note saying the outline-color may be ignored if outline-style is auto
From: Timeless
Comment: http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com
Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html
Closed: Rejected
Resolved: Editors' discretion
Verified: https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html
Note: Reject, this is already stated 2 lines above.

----
Issue 99.
Summary: spec unclear as to what the limits of the area where the cursor should apply are when using border-radius
From: Florian Rivoal
Comment: http://www.w3.org/mid/020131AE-4EBD-4504-82A6-6C14C44A2DD8@rivoal.net
Response: http://www.w3.org/mid/558196B1.8070007@inkedblade.net
Resolve: Bugfix
Closed: Accepted

----
Issue 100.
Summary: Non standard error handling for unsupported cursor value considered harmful
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jun/0195.html
Comment: http://www.w3.org/mid/CADhPm3uC4djOME_7i60YmHW5f0eCddU91eJhk96+wzdoYanDNA@mail.gmail.com
Resolved: http://www.w3.org/mid/791CA58E-34E8-4396-A726-04CF6CD3AF8E@rivoal.net
Closed: Accepted

----
Issue 101.
Summary: Drop "should not apply" text, make it apply when UAs implement the CSSPseudoElement Interface
From: Florian Rivoal
Comment: https://lists.w3.org/Archives/Public/www-style/2015Mar/0051.html
Closed: Deferred
Verified: reporter is spec editor
Note: Previously registered as part of issue 81

----
Issue 102.
Summary: Warn about what third parties may do in case of non conformance with acessibility requirement
From: timeless
Comment: http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com
Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html
Closed: OutOfScope
Verified: https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html
Note: 2015-06-10 WG telcon resolved to reject threat request, as out of scope for a W3C spec.
Note: Previously part of Issue 97.
----
Issue 103.
Summary: Consider not dropping the padding-box value of the box-sizing property
From: Florian Rivoal, Jonathan Kingston
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jun/0123.html
Comment: https://lists.w3.org/Archives/Public/www-style/2015Jun/0269.html
Resolved: https://lists.w3.org/Archives/Public/www-style/2015Jun/0241.html
Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0323.html
Verified: https://lists.w3.org/Archives/Public/www-style/2015Jun/0327.html
Closed: Rejected
Note: All browser vendors agree on not implementing this feature.
