diff --git a/css-animations/Overview.bs b/css-animations/Overview.bs index c89af4368b5..e7fdfda44e4 100644 --- a/css-animations/Overview.bs +++ b/css-animations/Overview.bs @@ -51,6 +51,8 @@ urlPrefix: https://html.spec.whatwg.org/multipage/infrastructure.html; type: dfn 
 spec:cssom-1; type:interface; text:CSSRule
 spec:html; type:dfn; text:case-sensitive
+spec:css-backgrounds-3; type:property; text:background-image
+spec:css2; type:property; text:display

@@ -787,19 +789,19 @@ The 'animation-fill-mode' property

is an integer greater than zero, the values applied will be those for the end of the last completed iteration of the animation (rather than the values for the start of the iteration that would be next). When 'animation-iteration-count' is zero, the values applied will be - those that would start the first iteration (just as when 'animation-fill-mode' is ''backwards''). + those that would start the first iteration (just as when 'animation-fill-mode' is ''animation-fill-mode/backwards'').
backwards
During the period defined by 'animation-delay', the animation will apply the property values defined in the keyframe that will start the first iteration of the animation. - These are either the values of the ''from'' keyframe (when 'animation-direction' is ''normal'' - or ''alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''reverse'' - or ''alternate-reverse''). + These are either the values of the ''from'' keyframe (when 'animation-direction' is ''animation-direction/normal'' + or ''animation-direction/alternate'') or those of the ''to'' keyframe (when 'animation-direction' is ''animation-direction/reverse'' + or ''animation-direction/alternate-reverse'').
both
- The effects of both ''forwards'' and ''backwards'' fill apply. + The effects of both ''animation-fill-mode/forwards'' and ''animation-fill-mode/backwards'' fill apply.

diff --git a/css-break/Overview.bs b/css-break/Overview.bs index 9b38581a8ff..85605e4a56a 100644 --- a/css-break/Overview.bs +++ b/css-break/Overview.bs @@ -1076,7 +1076,8 @@ Transforms, Positioning, and Pagination

(The origin of an overflow-only fragment is determined as if that content were overflowing an empty box with zero margins/borders/padding at the start of the fragmentainer.) - However, the separation and transfer of page boxes should occur last; + However, in order to reduce dataloss when printing, + the separation and transfer of page boxes should occur last; thus a transformed fragment that spans pages should be sliced at the page breaks and print in its entirety rather than being clipped by its originating page. @@ -1093,11 +1094,13 @@ Transforms, Positioning, and Pagination

Absolute positioning affects layout and thus interacts with fragmentation. Both the coordinate system and absolutely-positioned boxes belonging to a containing block - will fragment across pages in the same fragmentation flow as the containing block. + will fragment across fragmentainers in the same fragmentation flow as the containing block.

UAs are not required to correctly position boxes that span a fragmentation break and whose block-start edge position depends on where the box's content fragments. + +

UAs with memory constraints that prevent them from manipulating an entire document in memory are not required to correctly position absolutely-positioned elements that end up on a previously-rendered page. diff --git a/css-content/Overview.bs b/css-content/Overview.bs index ab600987469..96ea34bfd2d 100644 --- a/css-content/Overview.bs +++ b/css-content/Overview.bs @@ -16,6 +16,7 @@ Ignored Terms: , leader(), string(), target-counter(), target-counters Abstract: This CSS3 Module describes how to insert content in a document. Link Defaults: css21 (type) , css-display-3 (value) inline Status Text: This is a very rough draft, and is not ready for implementation. +Default Highlight: css @@ -34,156 +35,230 @@ Status Text: This is a very rough draft, and is not ready for implementation. !-->

- Introduction -

+Introduction + Authors sometimes want user agents to render content that does not come from the document tree. + One familiar example of this is numbered headings; + the author does not want to mark the numbers up explicitly, + they want the user agent to generate them automatically. + Counters and markers are used to achieve these effects. -Authors sometimes want user agents to render content that does not come from the document tree. One familiar example of this is numbered headings; the author does not want to mark the numbers up explicitly, she or he wants the user agent to generate them automatically. Counters and markers are used to achieve these effects. -
-
-h1::before { content: counter(section) ": "; }
-
-
+
+ 
+		h1::before { content: counter(section) ": "; }
+
+
-Similarly, authors may want the user agent to insert the word "Figure" before the caption of a figure, or "Chapter 7" on a line before the seventh chapter title. + Similarly, authors may want the user agent to insert the word "Figure" before the caption of a figure, + or "Chapter 7" on a line before the seventh chapter title. -
-
-chapter { counter-increment: chapter; }
-chapter > title::before { content: "Chapter " counter(chapter) "\A"; }
-
-
+
+ 
+		chapter { counter-increment: chapter; }
+		chapter > title::before { content: "Chapter " counter(chapter) "\A"; }
+
+
-Another common effect is replacing elements with images or other multimedia content. Since not all user agents support all multimedia formats, fallbacks may have to be provided. + Another common effect is replacing elements with images or other multimedia content. + Since not all user agents support all multimedia formats, + fallbacks may have to be provided. -
-
-/* Replace <logo> elements with the site's logo, using a format
- * supported by the UA */
-logo { content: url(logo.mov), url(logo.mng), url(logo.png), none; }
+	

+		
+		/* Replace <logo> elements with the site's logo, using a format
+		 * supported by the UA */
+		logo { content: url(logo.mov), url(logo.mng), url(logo.png), none; }
+
+		/* Replace <figure> elements with the referenced document, or,
+		 * failing that, with either the contents of the alt attribute or the
+		 * contents of the element itself if there is no alt attribute */
+		figure[alt] { content: attr(href, url), attr(alt); }
+		figure:not([alt]) { content: attr(href, url), contents; }
+		

+	

 
-/* Replace <figure> elements with the referenced document, or,
- * failing that, with either the contents of the alt attribute or the
- * contents of the element itself if there is no alt attribute */
-figure[alt] { content: attr(href, url), attr(alt); }
-figure:not([alt]) { content: attr(href, url), contents; }
-
-
+

+Inserting and replacing content with the 'content' property

+ 
+		Name: content
+		Value: normal | none | [ <> | <> ] [/ <> ]?
+		Initial: normal
+		Applies To: all elements, tree-abiding pseudo-elements, and page margin boxes
+		Inherited: no
+		Percentages: n/a
+		Computed Value: As specified below
+		Media: all
+
-

Inserting and replacing content with the 'content' property

+ The 'content' property dictates what is rendered inside an element or pseudo-element. -
-    Name: content
-    Value: [ <> ',' ]* [ normal | none | <> ] [/ <> ]?
-    Initial: normal
-    Applies To: ''::before'', ''::after'', ''::marker'',  and page margin boxes. Image and url values can apply to all elements. 
-    Inherited: no
-    Percentages: n/a
-    Computed Value: As specified below.
-    Media: all
-
+ For elements, it has only one purpose: + specifying that the element renders as normal, + or replacing the element with an image + (and possibly some associated "alt text"). + For pseudo-elements and margin boxes, + it is more powerful. + It controls whether the element renders at all, + can replace the element with an image, + or replace it with arbitrary inline content + (text and images). -The 'content' property dictates what is rendered inside the element or pseudo-element. It takes a comma separated list of URIs, followed by a space separated list of tokens, followed by an optional slash and string indicating alternative text. If there are multiple URIs provided, then each is tried in turn until a value which is both available and supported is found. The last value is used as a fallback if the others fail. +
+
normal +
+ For an element, this computes to ''content/contents''. + For ''::before'' and ''::after'', this computes to ''content/none''. +
none +
+ On elements, this inhibits the children of the element from being rendered as children of this element, + as if the element was empty. + On pseudo-elements it inhibits the creation of the pseudo-element as if it had ''display: none''. -
+ In neither case does it prevent any pseudo-elements which have this element or pseudo-element as an originating element from being generated. -
normal -
For an element, this computes to ''content/contents''. +
<> +
+ Equal to: - For ''::before'' and ''::after'', this computes to ''inhibit''. + 
<>
-
none -
On elements, this inhibits the children of the element from being rendered as children of this element, as if the element was empty. + Makes the element or pseudo-element a replaced element, + filled with the specified <>. + Its normal contents are suppressed + and do not generate boxes, + as if they were ''display: none''. - On pseudo-elements it inhibits the creation of the pseudo-element as if it had ''display: none''. + If the <> represents an invalid image, + then it must be treated as instead representing an image with zero intrinsic width and height, + filled with transparent black. - In neither case does it prevent any pseudo-elements which have this element or pseudo-element as an originating element from being generated. + Issue: The above invalid image behavior appears to be what Chrome is doing. + Is this okay? + Is there a better behavior we can/should use? + Issue: "Zero intrinsic width and height" gives it an undefined aspect ratio, + and sizing behavior is thus... undefined. + At least, if you give it an explicit width or height, + the other dimension remains at zero in Chrome. + This might need to be explicitly defined over in the Images spec; + needs some investigation around whether browsers act this way for 0x0 SVGs and rasters. + Note: Replaced elements use different layout rules than normal elements. + (In effect, it becomes equivalent to an HTML <{img}> element.) -
<> -
- [ <> | contents | <> | <> | ''document-url'' | <> | ''leader()'' ]+ + Note: Replaced elements do not have ''::before'' or ''::after'' pseudo-elements; + the 'content' property replaces their entire contents. -See sections below for details on each of these. +
<> +
+ Equal to: -
+ 
+			[ <> | contents | <> | <> | ''document-url'' | <> | ''leader()'' ]+
+
-Issue: Should the contents keyword be replaced with ''content()''? + Replaces the element's contents with oen or more anonymous inline boxes + corresponding to the specified values, + in the order specified. + Its normal contents are suppressed + and do not generate boxes, + as if they were ''display: none''. + Each value contributes an inline box to the element's contents. + For <>, this is an inline anonymous replaced element; + for the others, it's an anonymous inline run of text. + If an <> represents an invalid image, + the user agent must do one of the following: + * "Skip" the <>, generating nothing for it. + * Display some indication that the image can't be displayed in place of the <>, + such as a "broken image" icon. + This specification intentionally does not define which behavior a user agent must use, + but it must use one or the other consistently. -

If the computed value of the part of the 'content' property that ends up being used is a single URI, then the element or pseudo-element is a replaced element. The box model defines different rules for the layout of replaced elements than normal elements. Replaced elements do not have '::before' and '::after' pseudo-elements; the 'content' property in the case of replaced content replaces the entire contents of the element's box. + Note: If the value of <> is a single <>, + it must instead be interpreted as a <>. + +

/ <> +
+ Specifies the "alt text" for the element. + See [[#alt]] for details. + If omitted, + the element has no "alt text". +
+ + Issue: Should the contents keyword be replaced with ''content()''?

Accessibility of Generated Content

- Generated content should be searchable, selectable, and available to assistive technologies. - The 'content' property applies to speech - and generated content must be rendered for speech output. [[!CSS3-SPEECH]] + Generated content should be searchable, selectable, and available to assistive technologies. + The 'content' property applies to speech + and generated content must be rendered for speech output. [[!CSS3-SPEECH]] - Issue: Start work on an AAM for CSS. + Issue: Start work on an AAM for CSS.

Alternative Text for Speech

- Content intended for visual media sometimes needs alternative text for speech output. - The 'content' property thus accepts alternative text - to be specified after a slash (''/'') after the last <>. - If such alternative text is provided, - it must be used for speech output instead. + Content intended for visual media sometimes needs alternative text for speech output. + The 'content' property thus accepts alternative text + to be specified after a slash (''/'') after the last <>. + If such alternative text is provided, + it must be used for speech output instead. - This allows, for example, purely decorative text to be elided in speech output - (by providing the empty string as alternative text), - and allows authors to provide more readable alternatives - to images, icons, or text-encoded symbols. + This allows, for example, purely decorative text to be elided in speech output + (by providing the empty string as alternative text), + and allows authors to provide more readable alternatives + to images, icons, or text-encoded symbols. - + -
- Here the content property is an image, so the alt value is required to provide alternative text. +
+ Here the content property is an image, so the alt value is required to provide alternative text. - 
-	  .new::before {
-	    content: url(./img/star.png) / "New!";
-        /* or a localized attribute from the DOM: attr("data-alt") */
-	  }
-
-
+ 
+		.new::before {
+		 content: url(./img/star.png) / "New!";
+			/* or a localized attribute from the DOM: attr("data-alt") */
+		}
+
+
-
- If the pseudo-element is purely decorative and its function is covered elsewhere, setting alt to the empty string can avoid reading out the decorative element. Here the ARIA attribute will be spoken as "collapsed". Without the empty string alt value, the content would also be spoken as "Black right-pointing pointer". +
+ If the pseudo-element is purely decorative and its function is covered elsewhere, setting alt to the empty string can avoid reading out the decorative element. Here the ARIA attribute will be spoken as "collapsed". Without the empty string alt value, the content would also be spoken as "Black right-pointing pointer". - 
-	  .expandable::before {
-	    content: "\25BA" / ""; 
+		
+		.expandable::before {
+		 content: "\25BA" / "";
 		/* a.k.a. ► */
-	    /* aria-expanded="false" already in DOM,
-	       so this pseudo-element is decorative */
-	  }
-	  

-
+ /* aria-expanded="false" already in DOM, + so this pseudo-element is decorative */ + } + +
- +

-Content Values and Functions

+<> Values and Functions - The 'content' property can be used to add many different types of content to a document, - including images, strings, the values of counters, and the text value of elements. - In this section we enumerate the possibilities. + The <> value is used in 'content' + to fill an element with one or more anonymous inline boxes, + including images, strings, the values of counters, and the text value of elements. + In this section we enumerate the possibilities.

@@ -192,281 +267,311 @@ String

<>
- The element or pseudo-element contains the specified string. Occurrences of white space characters in the string are handled according to the properties given in the [[CSS3TEXT]] module. - + Represents an anonymous inline box filled with the specified text. + + Note: White space in the string is handled the same as in literal text, + and controlled by the properties in [[CSS-TEXT-3]] and elsewhere. + In particular, white space character can collapse, + even across multiple strings, + such as in ''content: "First " " Second";'', + which by default will render similar to "First Second" + (with a single visible space between the two words).

-URI

- -
-
<>
-
For URIs other than URIs in the last comma separated section of the value, if the URI is available and the format is supported, then the element or pseudo-element becomes a replaced element, otherwise, the next item in the comma separated list is used, if any. -
- -
- 
-		h1 { content: url(header/mng), url(header/png), none; }
-
-
- - In the example above, if header/mng wasn't in a supported format, then header/png would have been used instead. In the example above, if header/png wasn't available either, then the <h1> element would be empty, as the last alternative is ''content/none''. - - To make an element fallback on its contents, you have to explicitly give ''content/contents'' as a fallback: - -
- 
content: url(1), url(2), url(3), contents;
-
- -

What happens when no formats are supported, and the author does not explicitly indicate a fallback? Why doesn't an element fallback to ''content/contents'' unless an author explicitly says so? - - If the URI is part of the last comma separated value in the list, as the second URI in the following example: - -

- 
h1 { content: url(welcome), "Welcome to: " url(logo); }
-
- - ...then if the file is available and the format is supported, then an anonymous replaced inline element is inserted, otherwise the image is ignored (as if it hadn't been given at all). - -

There appears to be some change from [[CSS21]] which says, "If the user agent cannot display the resource it must either leave it out as if it were not specified or display some indication that the resource cannot be displayed." Are we now saying that a user agent cannot display a missing image graphic in this situation? - - When a URI is used as replaced content, it affects the generation of ''::before'' and ''::after'' pseudo-elements. - - +<> +

+
<>
+
+ Represents an anonymous inline replaced element + filled with the specified <>. + If the <> represents an invalid image, + this value instead represents nothing. + (No inline content is added to the element, + as if this value were "skipped".) +
+ Issue: CSS2.1 explicitly allowed the UA to substitute a broken image icon + if the image was invalid. + However, no browser appears to do this. + Is this removal okay?

Element Content

-
+
contents -
The element's descendents. Since this can only be used once per element (you can't duplicate the children if, e.g., one is a plugin or form control), it is handled as follows: - +
+ The element's descendents. + Since this can only be used once per element + (you can't duplicate the children if, e.g., one is a plugin or form control), + it is handled as follows: : If set on the element: - :: Always honoured. Note that this is the default, since the initial value of 'content' is ''content/normal'' and ''content/normal'' computes to ''content/contents'' on an element. + :: Always honoured. + Note that this is the default, + since the initial value of 'content' is ''content/normal'' + and ''content/normal'' computes to ''content/contents'' on an element. : If set on one of the element's other pseudo-elements: :: Check to see that it is not set on a "previous" pseudo-element, in the following order, depth first: + 1. the element itself 2. ::before 3. ::after - Issue: Should this behave as an empty string on pseudo-elements? + Issue: Should this behave as an empty string on pseudo-elements? - If it is already used, then it evaluates to nothing (like ''content/none''). Only pseudo-elements that are actually generated are checked. - - -
- - -
- In the following case: - - 
-				foo { content: normal; }   /* this is the initial value */
-				foo::after { content: contents; }
-
- - ...the element's 'content' property would compute to ''content/contents'' and the after pseudo element would have no contents (equivalent to ''content/none'') and thus would not appear. + If it is already used, then it evaluates to nothing (like ''content/none''). + Only pseudo-elements that are actually generated are checked. +
- 
-				foo { content: none; }
-				foo::after { content: contents; }
-
- But in this example, the ::after pseudo-element will contain the contents of the foo element. - +
+ In the following case: -

Use cases for suppressing the content on the element and using it in a pseudo-element would be welcome. + 

+		foo { content: normal; }	/* this is the initial value */
+		foo::after { content: contents; }
+
- Note that while it is useless to include ''content/contents'' twice in a single 'content' property, that is not a parse error. The second occurrence simply has no effect, as it has already been used. It is also not a parse error to use it on a marker pseudo-element, it is only during the rendering stage that it gets treated like ''content/none''. + ...the element's 'content' property would compute to ''content/contents'' + and the after pseudo element would have no contents + (equivalent to ''content/none'') + and thus would not appear. -

Do we need the statement about marker pseudo-elements here? Or is this legacy from the old version of the spec? + 

+		foo { content: none; }
+		foo::after { content: contents; }
+
+ But in this example, the ::after pseudo-element will contain the contents of the foo element. +
+ ISSUE: Use cases for suppressing the content on the element and using it in a pseudo-element would be welcome. + Note: While it is useless to include ''content/contents'' twice in a single 'content' property, + that is not a parse error. + The second occurrence simply has no effect, + as it has already been used. + It is also not a parse error to use it on a ''::marker'' pseudo-element, + it is only during the rendering stage that it gets treated like ''content/none''. + Issue: Do we need the statement about marker pseudo-elements here? Or is this legacy from the old version of the spec?

Quotes

- HTML has long had the q element, used to delimit quotations. The ''quotes'' property, in conjunction with the various *-quote values of the 'content' property, can be used to properly style such quotations. + HTML has long had the q element, + used to delimit quotations. + The ''quotes'' property, + in conjunction with the various ''*-quote'' values of the 'content' property, + can be used to properly style such quotations.

Specifying quotes with the 'quotes' property

-
-    Name: quotes
-    Value: [ <> <> ]+ | none
-    Initial: depends on user agent
-    Applies To: all elements
-    Inherited: yes
-    Percentages: n/a
-    Computed Value: specified value
-    Media: all
-
- -

The previous ED had an initial value of ''text'', which was an error. [[CSS21]] has initial value of "depends on user agent". Do we use auto for things like this, or is it just a UA stylesheet issue? + 

+		Name: quotes
+		Value: [ <> <> ]+ | none
+		Initial: depends on user agent
+		Applies To: all elements
+		Inherited: yes
+		Percentages: n/a
+		Computed Value: specified value
+		Media: all
+
+ Issue: The previous ED had an initial value of ''text'', + which was an error. + [[CSS21]] has initial value of "depends on user agent". + Do we use auto for things like this, + or is it just a UA stylesheet issue? -This property specifies quotation marks for any number of embedded quotations. Values have the following meanings: + This property specifies quotation marks for any number of embedded quotations. Values have the following meanings: -
-
none -
The ''open-quote'' and ''close-quote'' values of the 'content' property produce no quotations marks, as if they were ''no-open-quote'' and ''no-close-quote'' respectively. +
+
none +
+ The ''open-quote'' and ''close-quote'' values of the 'content' property + produce no quotations marks, + as if they were ''no-open-quote'' and ''no-close-quote'' respectively. - + -
[ <> <> ]+ -
Values for the ''open-quote'' and ''close-quote'' values of the 'content' property are taken from this list of pairs of quotation marks (opening and closing). The first (leftmost) pair represents the outermost level of quotation, the second pair the first level of embedding, etc. The user agent must apply the appropriate pair of quotation marks according to the level of embedding. -
+
[ <> <> ]+ +
+ Values for the ''open-quote'' and ''close-quote'' values of the 'content' property + are taken from this list of pairs of quotation marks (opening and closing). + The first (leftmost) pair represents the outermost level of quotation, + the second pair the first level of embedding, etc. + The user agent must apply the appropriate pair of quotation marks according to the level of embedding. +

-The *-quote values of the content property -

- - +The *-quote values of the content property 
 		<> = [open-quote | close-quote | no-open-quote | no-close-quote]
- -
-
open-quote
close-quote -
These values are replaced by the appropriate string from the 'quotes' property, and increments (decrements) the level of nesting for quotes. See [[#quotes-property]] for more information. +
+ These values are replaced by the appropriate string from the 'quotes' property, + and increments (decrements) the level of nesting for quotes. + See [[#quotes-property]] for more information. +
no-open-quote
no-close-quote -
Inserts nothing (as in ''content/none''), but increments (decrements) the level of nesting for quotes. See [[#quotes-property]] for more information. - +
+ Inserts nothing (as in ''content/none''), + but increments (decrements) the level of nesting for quotes. + See [[#quotes-property]] for more information.
- Quotation marks are inserted in appropriate places in a document with the ''open-quote'' and ''close-quote'' values of the 'content' property. Each occurrence of ''open-quote'' or ''close-quote'' is replaced by one of the strings from the value of 'quotes', based on the depth of nesting. + Quotation marks are inserted in appropriate places in a document + with the ''open-quote'' and ''close-quote'' values of the 'content' property. + Each occurrence of ''open-quote'' or ''close-quote'' + is replaced by one of the strings from the value of 'quotes', + based on the depth of nesting. - ''open-quote'' refers to the first of a pair of quotes, ''close-quote'' refers to the second. Which pair of quotes is used depends on the nesting level of quotes: the number of occurrences of ''open-quote'' in all generated text before the current occurrence, minus the number of occurrences of ''close-quote''. If the depth is 0, the first pair is used, if the depth is 1, the second pair is used, etc. If the depth is greater than the number of pairs, the last pair is repeated. + ''open-quote'' refers to the first of a pair of quotes, + ''close-quote'' refers to the second. + Which pair of quotes is used depends on the nesting level of quotes: + the number of occurrences of ''open-quote'' in all generated text before the current occurrence, + minus the number of occurrences of ''close-quote''. + If the depth is 0, the first pair is used, + if the depth is 1, the second pair is used, etc. + If the depth is greater than the number of pairs, + the last pair is repeated. Note that this quoting depth is independent of the nesting of the source document or the formatting structure. - Some typographic styles require open quotation marks to be repeated before every paragraph of a quote spanning several paragraphs, but only the last paragraph ends with a closing quotation mark. In CSS, this can be achieved by inserting "phantom" closing quotes. The keyword ''no-close-quote'' decrements the quoting level, but does not insert a quotation mark. + Some typographic styles require open quotation marks to be repeated + before every paragraph of a quote spanning several paragraphs, + but only the last paragraph ends with a closing quotation mark. + In CSS, this can be achieved by inserting "phantom" closing quotes. + The keyword ''no-close-quote'' decrements the quoting level, + but does not insert a quotation mark.
- The following style sheet puts opening quotation marks on every paragraph in a blockquote, and inserts a single closing quote at the end: - - 
-		blockquote p:before { content: open-quote }
-		blockquote p:after { content: no-close-quote }
-		blockquote p:last-child::after { content: close-quote }
-
+ The following style sheet puts opening quotation marks on every paragraph in a blockquote, and inserts a single closing quote at the end: + 
+			blockquote p:before { content: open-quote }
+			blockquote p:after { content: no-close-quote }
+			blockquote p:last-child::after { content: close-quote }
+
- For symmetry, there is also a ''no-open-quote'' keyword, which inserts nothing, but increments the quotation depth by one. + For symmetry, there is also a ''no-open-quote'' keyword, + which inserts nothing, + but increments the quotation depth by one. -
If a quotation is in a different language than the surrounding text, it is customary to quote the text with the quote marks of the language of the surrounding text, not the language of the quotation itself. -
+ Note: If a quotation is in a different language than the surrounding text, + it is customary to quote the text with the quote marks of the language of the surrounding text, + not the language of the quotation itself.
- For example, French inside English: - -
- The device of the order of the garter is “Honi soit qui mal y pense.” -
+ For example, French inside English: - English inside French: +
+ The device of the order of the garter is “Honi soit qui mal y pense.” +
-
- Il disait: « Il faut mettre l’action en ‹ fast - forward ›. » -
- - A style sheet like the following will set the 'quotes' property so that ''open-quote'' and ''close-quote'' will work correctly on all elements. These rules are for documents that contain only English, French, or both. One rule is needed for every additional language. Note the use of the child combinator (">") to set quotes on elements based on the language of the surrounding text: - - 
-	:lang(fr) > * { quotes: "\00AB\2005" "\2005\00BB" "\2039\2005" "\2005\203A" }
-	:lang(en) > * { quotes: "\201C" "\201D" "\2018" "\2019" }
-
+ English inside French: +
+ Il disait: « Il faut mettre l’action en ‹ fast forward ›. » +
+ A style sheet like the following will set the 'quotes' property + so that ''open-quote'' and ''close-quote'' will work correctly on all elements. + These rules are for documents that contain only English, French, or both. + One rule is needed for every additional language. + Note the use of the child combinator (">") + to set quotes on elements based on the language of the surrounding text: - The quotation marks are shown here in a form that most people will be able to type. If you can type them directly, they will look like this: + 
+		:lang(fr) > * { quotes: "\00AB\2005" "\2005\00BB" "\2039\2005" "\2005\203A" }
+		:lang(en) > * { quotes: "\201C" "\201D" "\2018" "\2019" }
+
- 
-	:lang(fr) > * { quotes: "« " " »" "‹ " " ›" }
-	:lang(en) > * { quotes: "“" "”" "‘" "’" }
+		The quotation marks are shown here in a form that most people will be able to type.
+		If you can type them directly, they will look like this:
 
-
+ 
+		:lang(fr) > * { quotes: "« " " »" "‹ " " ›" }
+		:lang(en) > * { quotes: "“" "”" "‘" "’" }
+
+
+ For example, applying the following style sheet: + 
+		/* Specify pairs of quotes for two levels in two languages */
+		:lang(en) > q { quotes: '"' '"' "'" "'" }
+		:lang(no) > q { quotes: "«" "»" "’" "’" }
 
-

-
-For example, applying the following style sheet:
-
-
-/* Specify pairs of quotes for two levels in two languages */
-:lang(en) > q { quotes: '"' '"' "'" "'" }
-:lang(no) > q { quotes: "«" "»" "’" "’" }
-
-/* Insert quotes before and after Q element content */
-q::before { content: open-quote }
-q::after  { content: close-quote }
-

+		/* Insert quotes before and after Q element content */
+		q::before { content: open-quote }
+		q::after	{ content: close-quote }
+
-to the following HTML fragment: - -
-<html lang="en">
-  <head>
-    <title>Quotes</title>
-  </head>
-  <body>
-    <p><q>Quote me!</q></p>
-  </body>
-</html>
-
+ to the following HTML fragment: + + 
+		<html lang="en">
+			<head>
+			 <title>Quotes</title>
+			</head>
+			<body>
+			 <p><q>Quote me!</q></p>
+			</body>
+		</html>
+
-would allow a user agent to produce: + would allow a user agent to produce: -
-"Quote me!"
-
+ 
+		"Quote me!"
+
-while this HTML fragment: - -
-<html lang="no">
-  <head>
-    <title>Quotes</title>
-  </head>
-  <body>
-    <p><q>Trøndere gråter når <q>Vinsjan på kaia</q> blir deklamert.</q></p>
-  </body>
-</html>
-
+ while this HTML fragment: + + 
+		<html lang="no">
+			<head>
+			 <title>Quotes</title>
+			</head>
+			<body>
+			 <p><q>Trøndere gråter når <q>Vinsjan på kaia</q> blir deklamert.</q></p>
+			</body>
+		</html>
+
-would produce: + would produce: -
-«Trøndere gråter når ’Vinsjan på kaia’ blir deklamert.»
-
-
+ 
+		«Trøndere gråter når ’Vinsjan på kaia’ blir deklamert.»
+
+ @@ -475,19 +580,28 @@ would produce:

Leaders

- A leader, sometimes known as a tab leader or a dot leader, is a repeating pattern used to visually connect content across horizontal spaces. They are most commonly used in tables of contents, between titles and page numbers. The ''leader()'' function, as a value for the content property, is used to create leaders in CSS. This function takes a string (the leader string), which describes the repeating pattern for the leader. + A leader, sometimes known as a tab leader or a dot leader, + is a repeating pattern used to visually connect content across horizontal spaces. + They are most commonly used in tables of contents, + between titles and page numbers. + The ''leader()'' function, + as a value for the content property, + is used to create leaders in CSS. + This function takes a string (the leader string), + which describes the repeating pattern for the leader.

-The ''leader()'' function -

+The ''leader()'' function -
-
leader() -
Inserts a leader. See the section on leaders for more information. +
+
leader( <> ) +
+ Inserts a leader. + See the section on leaders for more information. 
-		leader() = leader( dotted | solid | space | <>);
+		<> = leader( dotted | solid | space | <>);
Three keywords are shorthand values for common strings: @@ -501,121 +615,147 @@ The ''leader()'' function
Equivalent to ''leader(" ")''
<>
- Issue: Define this. + Issue: Define this.
-
- 
-	ol.toc a::after {
-	  content: leader('.') target-counter(attr(href), page);
-	}
+	

+		
+		ol.toc a::after {
+			content: leader('.') target-counter(attr(href), page);
+		}
 
-	<h1>Table of Contents</h1>
-	<ol class="toc">
-	<li><a href="#chapter1">Loomings</a></li>
-	<li><a href="#chapter2">The Carpet-Bag</a></li>
-	<li><a href="#chapter3">The Spouter-Inn</a></li>
-	</ol>
+		<h1>Table of Contents</h1>
+		<ol class="toc">
+		<li><a href="#chapter1">Loomings</a></li>
+		<li><a href="#chapter2">The Carpet-Bag</a></li>
+		<li><a href="#chapter3">The Spouter-Inn</a></li>
+		</ol>
 
-	

+
- This might result in: + This might result in: - 
-	Table of Contents
+		
+		Table of Contents
 
-	1. Loomings.....................1
-	2. The Carpet-Bag...............9
-	3. The Spouter-Inn.............13
-	

-
+ 1. Loomings.....................1 + 2. The Carpet-Bag...............9 + 3. The Spouter-Inn.............13 + + -

-Do leaders depend on the assumption that the content after the leader is right-aligned (end-aligned)? + Issue: Do leaders depend on the assumption that the content after the leader is right-aligned (end-aligned)?

-Rendering leaders -

+Rendering leaders + + Consider a line which contains the content before the leader (the “before content”), + the leader, + and the content after the leader (the “after content”). + Leaders obey the following rules: + + 1. The leader string must appear in full at least once. + 2. The leader should be as long as possible + 3. Visible characters in leaders should vertically align with each other when possible. + 4. Line break characters in the leader string must be ignored. + 5. White space in the leader string follows normal CSS rules. + 6. A leader only appears between the start content and the end content. + 7. A leader only appears on a single line, even if the before content and after content are on different lines. + 8. A leader can’t be the only thing on a line. - Consider a line which contains the content before the leader (the “before content”), the leader, and the content after the leader (the “after content”). Leaders obey the following rules: -
    -
  1. The leader string must appear in full at least once. -
  2. The leader should be as long as possible -
  3. Visible characters in leaders should vertically align with each other when possible. -
  4. Line break characters in the leader string must be ignored. -
  5. White space in the leader string follows normal CSS rules. -
  6. A leader only appears between the start content and the end content. -
  7. A leader only appears on a single line, even if the before content and after content are on different lines. -
  8. A leader can’t be the only thing on a line. -

-Procedure for rendering leaders -

-
    -
  1. Lay out the before content, until reaching the line where the before content ends. 
    -BBBBBBBBBB
-BBB
-
    -
  2. The leader string consists of one or more glyphs, and is thus an inline box. A leader is a row of these boxes, drawn from the end edge to the start edge, where only those boxes not overlaid by the before or after content. On this line, draw the leader string, starting from the end edge, repeating as many times as possible until reaching the start edge. +Procedure for rendering leaders + 1. Lay out the before content, + until reaching the line where the before content ends. - + 2. The leader string consists of one or more glyphs, + and is thus an inline box. + A leader is a row of these boxes, + drawn from the end edge to the start edge, + where only those boxes not overlaid by the before or after content. + On this line, + draw the leader string, + starting from the end edge, + repeating as many times as possible until reaching the start edge. + - + Insert a line break after the before content, + draw the leader on the next line, + and draw the after content on top, + and hide any leader strings that are not fully displayed. -Issue: what to do if after content is wider than the line box? + 
    +		BBBBBBB
+		BBBBBB
+		......A
+
    + + -
    -drawing leaders -
    Procedure for drawing leaders
    -
    + Issue: what to do if after content is wider than the line box? + Issue: Leaders don't quite work in table layouts. How can we fix this? +
    + drawing leaders +
    Procedure for drawing leaders
    +
    -
    -drawing leaders -
    Procedure for drawing leaders when the content doesn’t fit on a single line
    -
    +
    + drawing leaders +
    Procedure for drawing leaders when the content doesn’t fit on a single line
    +

    -Cross references and the target-* functions -

    +Cross references and the target-* functions Many documents contain internal references: -
      -
    • See chapter 7 -
    • in section 4.1 -
    • on page 23 -
    - Three new values for the content property are used to automatically create these types of cross-references: ''target-counter()'', ''target-counters()'', and ''target-text()''. Each of these displays information obtained from the target end of a link. +
    + * See chapter 7 + * in section 4.1 + * on page 23 +
    + + Three new values for the content property + are used to automatically create these types of cross-references: + ''target-counter()'', ''target-counters()'', and ''target-text()''. + Each of these displays information obtained from the target end of a link. 
     		<> = [ ''target-counter()'' | ''target-counters()'' | ''target-text()'' ]
@@ -626,510 +766,559 @@ Cross references and the target-* functions
 
 
 
    
-The ''target-counter()'' function
-
    
+The ''target-counter()'' function
 
 	
     		target-counter() = target-counter( [ <> | <> ] , <> [ , <> ]? )
 	
    
 
-	The ''target-counter()'' function retrieves the value of the innermost counter with a given name. The required arguments are the url of the target and the name of the counter. An optional counter-style argument can be used to format the result.
+	The ''target-counter()'' function retrieves the value
+	of the innermost counter with a given name.
+	The required arguments are the url of the target
+	and the name of the counter.
+	An optional counter-style argument can be used to format the result.
 
-	These functions only take a fragment URL which points to a location in the current document. If there’s no fragment, if the ID referenced isn't there, or if the URL points to an outside document, the user agent must treat that as an error.
+	These functions only take a fragment URL
+	which points to a location in the current document.
+	If there’s no fragment,
+	if the ID referenced isn't there,
+	or if the URL points to an outside document,
+	the user agent must treat that as an error.
 
 	Issue: what should error handling be?
 
 	Issue: restrict syntactically to local references for now.
 
-
 	
    
-	HTML:
+		HTML:
 
-	
    -	…which will be discussed on page <a href="#chapter4_sec2"></a>.
-	
    
-	CSS:
+		
    +		…which will be discussed on page <a href="#chapter4_sec2"></a>.
+		
    
 
-	
    -	a::after { content: target-counter(attr(href url), page) }
-	
    
-	Result:
-	
    -	…which will be discussed on page 137.
-	
    
-	
    
+		CSS:
 
-
    
-Page numbers in tables of contents can be generated automatically:
+		
    +		a::after { content: target-counter(attr(href url), page) }
+		
    
 
-HTML:
+		Result:
 
-
    -<nav>
-  <ol>
-    <li class="frontmatter"><a href="#pref_01">Preface</a></li>
-    <li class="frontmatter"><a href="#intr_01">Introduction</a></li>
-    <li class="bodymatter"><a href="#chap_01">Chapter One</a></li>
-  </ol>
-</nav>
-
    
+		
    +		…which will be discussed on page 137.
+		
    
+	
    
 
-CSS:
+	
    
+		Page numbers in tables of contents can be generated automatically:
 
-
    -.frontmatter a::after { content: leader('.') target-counter(attr(href url), page, lower-roman) }
-.bodymatter a::after { content: leader('.') target-counter(attr(href url), page, decimal) }
-
    
+		HTML:
 
-Result:
+		
    +		<nav>
+			<ol>
+			 <li class="frontmatter"><a href="#pref_01">Preface</a></li>
+			 <li class="frontmatter"><a href="#intr_01">Introduction</a></li>
+			 <li class="bodymatter"><a href="#chap_01">Chapter One</a></li>
+			</ol>
+		</nav>
+		
    
 
-
    -Preface.............vii
-Introduction.........xi
-Chapter One...........1
-
    
+		CSS:
 
-
    
+		
    +		.frontmatter a::after { content: leader('.') target-counter(attr(href url), page, lower-roman) }
+		.bodymatter a::after { content: leader('.') target-counter(attr(href url), page, decimal) }
+		
    
+
+		Result:
+
+		
    +		Preface.............vii
+		Introduction.........xi
+		Chapter One...........1
+		
    
+	
 
 
 
 
    
 The ''target-counters()'' function
 
    
-This functions fetches the value of all counters of a given name from the end of a link, and formats them by inserting a given string between the value of each nested counter.
 
-
    -	target-counters() = target-counter( [ <> | <> ] , <> , <> [ , <> ]? )
-
    
-
-
    
+	This functions fetches the value of all counters of a given name
+	from the end of a link,
+	and formats them by inserting a given string between the value of each nested counter.
 
-
    -I have not found a compelling example for target-counters() yet.
-
    
+	
    +		target-counters() = target-counter( [ <> | <> ] , <> , <> [ , <> ]? )
+	
    
 
-Issue: found a compelling example, in CSS specs. Do something.
+	
    
+		
    +		I have not found a compelling example for target-counters() yet.
+		
    
 
-
    
+		Issue: found a compelling example, in CSS specs. Do something.
+	
    
 
 
    
-The ''target-text()'' function
-
    
-The ''target-text()'' function retrieves the text value of the element referred to by the URL. An optional second argument specifies what content is retrieved, using the same values as the 'string-set' property above.
-
-
    -	target-text() = target-text( [ <> | <> ] [ , [ content | before | after | first-letter] ]? )
-
    
+The ''target-text()'' function
 
+	The ''target-text()'' function retrieves
+	the text value of the element referred to by the URL.
+	An optional second argument specifies what content is retrieved,
+	using the same values as the 'string-set' property above.
 
-
    A simpler syntax has been proposed by fantasai: http://lists.w3.org/Archives/Public/www-style/2012Feb/0745.html
-
    
-
    -…which will be discussed <a href="#chapter_h1_1">later</a>.
+	
    +		target-text() = target-text( [ <> | <> ] [ , [ content | before | after | first-letter] ]? )
+	
    
 
-a::after { content: ", in the chapter entitled " target-text(attr(href url)) }
 
-
     Result: …which will be discussed later, in the chapter entitled Loomings.
-
    
+	Issue: A simpler syntax has been proposed by fantasai:
+	http://lists.w3.org/Archives/Public/www-style/2012Feb/0745.html
 
+	
    
+		
    +		…which will be discussed <a href="#chapter_h1_1">later</a>.
 
+		a::after { content: ", in the chapter entitled " target-text(attr(href url)) }
+		
    
 
+		Result: …which will be discussed later, in the chapter entitled Loomings.
+	
    
 
 
 
    
 Named strings
    
 
-This section introduces named strings, which are the textual equivalent of counters and which have a distinct namespace from counters. Named strings follow the same nesting rules as counters. The 'string-set' property accepts values similar to the 'content' property, including the extraction of the current value of counters.
-
-Named strings are a convenient way to pull metadata out of the document for insertion into headers and footers. In HTML, for example, META elements contained in the document HEAD can set the value of named strings. In conjunction with attribute selectors, this can be a powerful mechanism:
-
-
    
-
    -meta[author] { string-set: author attr(author); }
-head > title { string-set: title contents; }
-@page:left {
-  @top {
-    text-align: left;
-    vertical-align: middle;
-    content: string(title);
-  }
-}
-@page:right {
-  @top {
-    text-align: right;
-    vertical-align: middle;
-    content: string(author);
-  }
-}
-
    
-
    
+	This section introduces named strings,
+	which are the textual equivalent of counters
+	and which have a distinct namespace from counters.
+	Named strings follow the same nesting rules as counters.
+	The 'string-set' property accepts values similar to the 'content' property,
+	including the extraction of the current value of counters.
+
+	Named strings are a convenient way to pull metadata out of the document
+	for insertion into headers and footers.
+	In HTML, for example,
+	META elements contained in the document HEAD
+	can set the value of named strings.
+	In conjunction with attribute selectors,
+	this can be a powerful mechanism:
 
+	
    
+		
    +		meta[author] { string-set: author attr(author); }
+		head > title { string-set: title contents; }
+		@page:left {
+			@top {
+			 text-align: left;
+			 vertical-align: middle;
+			 content: string(title);
+			}
+		}
+		@page:right {
+			@top {
+			 text-align: right;
+			 vertical-align: middle;
+			 content: string(author);
+			}
+		}
+		
    
+	
    
 
-
 
 
+	
 
 
 
    
-The string-set property
-
    
-
-
    -Name: string-set
-Value: [ <> <>+ ]# | none
-Initial: none
-Applies to: all elements, but not pseudo-elements
-Inherited: no
-Percentages: N/A
-Media: all
-Computed value: specified value
-
    
-
-The 'string-set' property copies the text content of an element into a ''named string'', which functions as a variable. The text content of this named string can be retrieved using the ''string()'' function. Since these variables may change on a given page, an optional second value for the ''string()'' function allows authors to choose which value on a page is used.
-
-
    
-	
    none
-	
    
-		The element does not set any named strings.
+The string-set property
+
+	
    +	Name: string-set
+	Value: [ <> <>+ ]# | none
+	Initial: none
+	Applies to: all elements, but not pseudo-elements
+	Inherited: no
+	Percentages: N/A
+	Media: all
+	Computed value: specified value
+	
    
 
-	
    [ <> <>+ ]#
-	
    
-		The element establishes one or more named strings,
-		corresponding to each comma-separated entry in the list.
+	The 'string-set' property copies the text content of an element into a ''named string'',
+	which functions as a variable.
+	The text content of this named string can be retrieved using the ''string()'' function.
+	Since these variables may change on a given page,
+	an optional second value for the ''string()'' function
+	allows authors to choose which value on a page is used.
 
-		For each entry, the <> gives the name of the named string.
-		It's followed by one or more <> values,
-		which are concatenated together to form the value of the named string.
-
    
+	
    
+		
    none
+		
    
+			The element does not set any named strings.
 
+		
    [ <> <>+ ]#
+		
    
+			The element establishes one or more named strings,
+			corresponding to each comma-separated entry in the list.
 
+			For each entry, the <> gives the name of the named string.
+			It's followed by one or more <> values,
+			which are concatenated together to form the value of the named string.
+	
    
 
 
 
 
+	
    
+		The following example captures the contents of H1 elements,
+		which represent chapter names in this hypothetical document.
 
+		
    H1 { string-set: chapter contents; }
    
 
+		When an H1 element is encountered,
+		the ''chapter'' string is set to the element's textual contents,
+		and the previous value of ''chapter'', if any, is overwritten.
+	
    
 
-
    
-	The following example captures the contents of H1 elements, which represent chapter names in this hypothetical document.
-
-	
    H1 { string-set: chapter contents; }
    
-
-	When an H1 element is encountered, the ''chapter'' string is set to the element's textual contents, and the previous value of ''chapter'', if any, is overwritten.
-
    
-
-
-
    The ''string()'' function
    
-
-
    -	string() = string( <> , [ first | start | last | first-except ]? )
-
    
-
-The ''string()'' function is used to copy the value of a named string to the document, via the 'content' property. This function requires one argument, the name of the named string. Since the value of a named string may change several times on a page (as multiple elements defining the string can appear) an optional second argument indicates which value of the named string should be used.
-
-
-
-
-The second argument of the ''string()'' function is one of the following keywords:
-
    
-	
    first
-	
    The value of the first assignment on the page is used. If there is no assignment on the page, the entry value is used. If no second argument is provided, this is the default value.
-	
    start
-	
    If the element is the first element on the page, the value of the first assignment is used. Otherwise the entry value is used. The entry value may be empty if the named string hasn’t yet appeared.
-	
    last
-	
    The exit value of the named string is used.
-	
    first-except
-	
    This is identical to ''string()/first'', except that the empty string is used on the page where the value is assigned.
-	
-	Issue: we may need to kill the entire content string. Is this necessary?
-
    
-
-
-
-The content values of named strings are assigned at the point when the content box of the element is first created (or would have been created if the element’s display value is none). The entry value for a page is the assignment in effect at the end of the previous page. The exit value for a page is the assignment in effect at the end of the current page.
-
-
-
-
    
-	CSS:
-
-	
    -	@page {
-	   size: 15cm 10cm;
-	   margin: 1.5cm;
 
-	   @top-left {
-	   content: "first: " string(heading, first);
-	   }
-	   @top-center {
-	   content: "start: " string(heading, start);
-	   }
-	    @top-right {
-	    content: "last: " string(heading, last);
-	   }
-	  }
+
    
+The ''string()'' function
    
 
-	h2 { string-set: heading content() }
+	
    +		string() = string( <> , [ first | start | last | first-except ]? )
 	
    
 
-	The following figures show the first, start, and last assignments of the “heading” string on various pages.
-
-	
    
-		
-		
    The ''string-set/start'' value is empty, as the string had not yet been set at the start of the page.
    
-	
    
-	
    
-		
-		
    Since the page starts with an h2, the ''string-set/start'' value is the value of that head.
    
-	
    
-	
    
-		
-		
    Since there’s not an h2 at the top of this page, the ''string-set/start'' value is the exit value of the previous page.
    
-	
    
-
    
-
-
-
-
-
-
+	The ''string()'' function is used to copy the value of a named string to the document,
+	via the 'content' property.
+	This function requires one argument,
+	the name of the named string.
+	Since the value of a named string may change several times on a page
+	(as multiple elements defining the string can appear)
+	an optional second argument indicates which value of the named string should be used.
 
+	The second argument of the ''string()'' function is one of the following keywords:
 
+	
    
+		
    first
+		
    
+			The value of the first assignment on the page is used.
+			If there is no assignment on the page,
+			the entry value is used.
+			If no second argument is provided,
+			this is the default value.
 
+		
    start
+		
    
+			If the element is the first element on the page,
+			the value of the first assignment is used.
+			Otherwise the entry value is used.
+			The entry value may be empty if the named string hasn’t yet appeared.
 
+		
    last
+		
    
+			The exit value of the named string is used.
 
+		
    first-except
+		
    
+			This is identical to ''string()/first'',
+			except that the empty string is used on the page where the value is assigned.
 
-
    The ''content()'' function
    
-
-
    -	content() = content( [text | before | after | first-letter | marker ]? )
-
    
-
-
-
    
-	
    text
-	
    The string value of the element.
-		If no value is specified in ''content()'',
-		it acts as if ''content()/text'' were specified.
-	
    before
-	
    The string value of the ''::before'' pseudo-element.
-	
    after
-	
    The string value of the ''::after'' pseudo-element.
-	
    first-letter
-	
    The first letter of the element, as defined for the ''::first-letter'' pseudo-element
-	
    marker
-	
    The string value of the ''::marker'' pseudo-element.
-
-
    
-
-
+			Issue: we may need to kill the entire content string. Is this necessary?
+	
    
 
+	The content values of named strings
+	are assigned at the point when the content box of the element is first created
+	(or would have been created if the element’s display value is none).
+	The entry value for a page
+	is the assignment in effect at the end of the previous page.
+	The exit value for a page
+	is the assignment in effect at the end of the current page.
 
-
    
-	HTML:
+	
    
+		CSS:
 
-	
    -	<h1>Loomings</h1>
-	
    
+		
    +		@page {
+			size: 15cm 10cm;
+			margin: 1.5cm;
+
+			@top-left {
+			content: "first: " string(heading, first);
+			}
+			@top-center {
+			content: "start: " string(heading, start);
+			}
+			 @top-right {
+			 content: "last: " string(heading, last);
+			}
+			}
+
+		h2 { string-set: heading content() }
+		
    
 
-	CSS:
+		The following figures show the first, start, and last assignments
+		of the “heading” string on various pages.
+
+		
    
+			
+			
    The ''string-set/start'' value is empty,
+			as the string had not yet been set at the start of the page.
    
+		
    
+
+		
    
+			
+			
    Since the page starts with an h2,
+			the ''string-set/start'' value is the value of that head.
    
+		
    
+
+		
    
+			
+			
    Since there’s not an h2 at the top of this page,
+			the ''string-set/start'' value is the exit value of the previous page.
    
+		
    
+	
    
 
-	
    -	h1::before { content: 'Chapter ' counter(chapter); }
-	h1 { string-set: header content(before) ':' content(text); }
-	h1::after { content: '.'; }
-	
    
 
-	The value of the named string “header” will be “Chapter 1: Loomings”.
-
    
 
-
    
-	HTML:
+
    
+The ''content()'' function
    
 
-	
    -	<section title="Loomings">
+	
    +		content() = content( [text | before | after | first-letter | marker ]? )
 	
    
 
-	CSS:
+	
    
+		
    text
+		
    The string value of the element.
+			If no value is specified in ''content()'',
+			it acts as if ''content()/text'' were specified.
 
-	
    -	section { string-set: header attr(title) }
-	
    
+		
    before
+		
    The string value of the ''::before'' pseudo-element.
 
-	The value of the “header” string will be “Loomings”.
-
    
+		
    after
+		
    The string value of the ''::after'' pseudo-element.
 
+		
    first-letter
+		
    The first letter of the element, as defined for the ''::first-letter'' pseudo-element
 
+		
    marker
+		
    The string value of the ''::marker'' pseudo-element.
+	
 
+	
    
+		HTML:
 
+		
    +		<h1>Loomings</h1>
+		
    
 
+		CSS:
 
+		
    +		h1::before { content: 'Chapter ' counter(chapter); }
+		h1 { string-set: header content(before) ':' content(text); }
+		h1::after { content: '.'; }
+		
    
 
+		The value of the named string “header” will be “Chapter 1: Loomings”.
+	
    
 
+	
    
+		HTML:
 
+		
    +		<section title="Loomings">
+		
    
 
+		CSS:
 
+		
    +		section { string-set: header attr(title) }
+		
    
 
+		The value of the “header” string will be “Loomings”.
+	
    
 
 
 
    
 Automatic counters and numbering: the 'counter-increment' and 'counter-reset' properties (moved)
    
 
-
    Now described in [[CSS3LIST]]
-
-
    Should this move back to CSS Content?
-
-
+	Issue: Now described in [[CSS3LIST]]
 
+	Issue: Should this move back to CSS Content?
 
 
 
    
-Bookmarks
-
    
-Some document formats, most notably PDF, allow the use of bookmarks as an aid to navigation. 
-Bookmarks provide a list of links to document elements, as well as text to label the links and a level value.  
-A bookmark has three properties: 'bookmark-level', 'bookmark-label', and 'bookmark-state'.
+Bookmarks
+
+	Some document formats,
+	most notably PDF,
+	allow the use of bookmarks as an aid to navigation.
+	Bookmarks provide a list of links to document elements,
+	as well as text to label the links and a level value.
+	A bookmark has three properties:
+	'bookmark-level', 'bookmark-label', and 'bookmark-state'.
 
-When a user activates a bookmark, the user agent must bring that reference point to the user's attention, exactly as if navigating to that element by fragment URL. This will also trigger matching the '':target'' pseudo-class. 
+	When a user activates a bookmark,
+	the user agent must bring that reference point to the user's attention,
+	exactly as if navigating to that element by fragment URL.
+	This will also trigger matching the '':target'' pseudo-class.
 
 
    
 bookmark-level
 
    
 
-The 'bookmark-level' property determines if a bookmark is created, and at what level. If this property is absent, or has value ''bookmark-level/none'', no bookmark should be generated, regardless of the values of 'bookmark-label' or 'bookmark-state'.
-
-
    -Name: bookmark-level
-Value: none | <integer>
-Initial: none
-Applies to: all elements
-Inherited: no
-Percentages: N/A
-Media: visual
-Computed value: specified value
-
    
-
    
-
    <integer>
-
    defines the level of the bookmark, with the top level being 1 (negative and zero values are invalid).
-
    none
-
    no bookmark is generated.
-
    
-
-
    
-
    -section h1 { bookmark-level: 1; }
-section section h1 { bookmark-level: 2; }
-section section section h1 { bookmark-level: 3; }
-
    
+	The 'bookmark-level' property determines if a bookmark is created,
+	and at what level.
+	If this property is absent,
+	or has value ''bookmark-level/none'',
+	no bookmark should be generated,
+	regardless of the values of 'bookmark-label' or 'bookmark-state'.
+
+	
    +	Name: bookmark-level
+	Value: none | <>
+	Initial: none
+	Applies to: all elements
+	Inherited: no
+	Percentages: N/A
+	Media: visual
+	Computed value: specified value
+	
    
 
-
    
+	
    
+		
    <>
+		
    defines the level of the bookmark, with the top level being 1 (negative and zero values are invalid).
+		
    none
+		
    no bookmark is generated.
+	
    
 
-  Note: Bookmarks do not need to create a strict hierarchy of levels. 
+	
    
+		
    +		section h1 { bookmark-level: 1; }
+		section section h1 { bookmark-level: 2; }
+		section section section h1 { bookmark-level: 3; }
+		
    
+	
    
 
+	Note: Bookmarks do not need to create a strict hierarchy of levels.
 
-  Issue: Should a bookmark be created for elements with display: none?
+	Issue: Should a bookmark be created for elements with display: none?
 
 
 
    
-bookmark-label
-
    
-
    -Name: bookmark-label
-Value: <content-list>
-Initial: content(text)
-Applies to: all elements
-Inherited: no
-Percentages: N/A
-Media: visual
-Computed value: specified value
-
    
-
    
-
    <content-list>
-
    <> is defined above, in the section on the 'string-set' property. The value of <> becomes the text content of the bookmark label.
-
-
    
-
-
    
-HTML:
-
-
    -<h1>Loomings</h1>
-
    
-CSS:
+bookmark-label
+
+	
    +	Name: bookmark-label
+	Value: <>
+	Initial: content(text)
+	Applies to: all elements
+	Inherited: no
+	Percentages: N/A
+	Media: visual
+	Computed value: specified value
+	
    
 
-
    -h1 {
-bookmark-label: content(text);
-bookmark-level: 1;
-}
-
    
-The bookmark label will be “Loomings”.
-
    
+	
    
+		
    <>
+		
    <> is defined above, in the section on the 'string-set' property. The value of <> becomes the text content of the bookmark label.
 
-
    
-bookmark-state
-
    
-The 'bookmark-state' may be open or closed. The user must be able to toggle the bookmark state.
-
-
    -Name: bookmark-state
-Value: open | closed
-Initial: open
-Applies to: block-level elements
-Inherited: no
-Percentages: N/A
-Media: visual
-Computed value: specified value
-
    
-
    
-
    open
-
    Subsequent bookmarks with 'bookmark-level' greater than the given bookmark are displayed, until reaching another bookmark of the same level or lower. If one of subsequent bookmark is closed, apply the same test to determine if its subsequent bookmarks should be displayed.
-
    closed
-
    Subsequent bookmarks of bookmark-level greater than the given bookmark are not displayed, until reaching another bookmark of the same level or lower. 
-
    
+		
+	
    
+
+	
    
+		HTML:
+
+		
    +		<h1>Loomings</h1>
+		
    
+
+		CSS:
 
-Issue: is the initial bookmark state, or the bookmark state updated by the UA as appropriate?
+		
    +		h1 {
+		bookmark-label: content(text);
+		bookmark-level: 1;
+		}
+		
    
+
+		The bookmark label will be “Loomings”.
+	
    
+
+
    
+bookmark-state
    
+
+	The 'bookmark-state' may be open or closed. The user must be able to toggle the bookmark state.
+
+	
    +	Name: bookmark-state
+	Value: open | closed
+	Initial: open
+	Applies to: block-level elements
+	Inherited: no
+	Percentages: N/A
+	Media: visual
+	Computed value: specified value
+	
    
 
+	
    
+		
    open
+		
    
+			Subsequent bookmarks with 'bookmark-level' greater than the given bookmark are displayed,
+			until reaching another bookmark of the same level or lower.
+			If one of subsequent bookmark is closed,
+			apply the same test to determine if its subsequent bookmarks should be displayed.
 
+		
    closed
+		
    
+			Subsequent bookmarks of bookmark-level greater than the given bookmark are not displayed,
+			until reaching another bookmark of the same level or lower.
+	
    
 
-
+		* what ::outside::before matches in this case
+	-->
 
 
    Changes since the 14 May 2003 Working Draft
    
 
-* Terminology section deleted, as that information is now in [[CSS-PSEUDO-4]]
+	* Terminology section deleted, as that information is now in [[CSS-PSEUDO-4]]
 
-* Pseudo-elements section replaced by [[CSS-PSEUDO-4]]
+	* Pseudo-elements section replaced by [[CSS-PSEUDO-4]]
 
-* Automatic counters and numbering section replaced by [[CSS3LIST]]
+	* Automatic counters and numbering section replaced by [[CSS3LIST]]
 
-* Section on Named strings replaced by content moved from [[CSS3GCPM]]
+	* Section on Named strings replaced by content moved from [[CSS3GCPM]]
 
-* Removed ''icon'' value of content property.
+	* Removed ''icon'' value of content property.
 
-* Removed ''<glyph>'' values of content property.
+	* Removed ''<glyph>'' values of content property.
 
-* Bookmarks, Cross References, and Leaders section moved from [[CSS3GCPM]] to this specification
+	* Bookmarks, Cross References, and Leaders section moved from [[CSS3GCPM]] to this specification
 
-* Removed mechanisms for moving document content around, including the ::alternate pseudo-element and the pending value of the 'content' property.
+	* Removed mechanisms for moving document content around, including the ::alternate pseudo-element and the pending value of the 'content' property.
 
-* Examples of Norwegian and French quotation marks no longer use plus signs and semicolons as delimiters.
+	* Examples of Norwegian and French quotation marks no longer use plus signs and semicolons as delimiters.
 
-* Dave Cramer added as co-editor. Ian Hickson and Håkon Wium Lie are now former editors.
+	* Dave Cramer added as co-editor. Ian Hickson and Håkon Wium Lie are now former editors.
 
 
    Acknowledgements
    
 
-Stuart Ballard, David Baron, Bert Bos, and Tantek Çelik provided invaluable suggestions used in this
-specification.
+	Stuart Ballard, David Baron, Bert Bos, and Tantek Çelik provided invaluable suggestions used in this specification.
 
 
diff --git a/css-font-loading/Overview.bs b/css-font-loading/Overview.bs
index 52431dfc04c..08dba1e4a5d 100644
--- a/css-font-loading/Overview.bs
+++ b/css-font-loading/Overview.bs
@@ -446,7 +446,7 @@ The FontFaceSet Interface
 		[Constructor(DOMString type, optional FontFaceSetLoadEventInit eventInitDict),
 		 Exposed=Window,Worker]
 		interface FontFaceSetLoadEvent : Event {
-			readonly attribute sequence<FontFace> fontfaces;
+			[SameObject] readonly attribute FrozenArray<FontFace> fontfaces;
 		};
 
 		enum FontFaceSetLoadStatus { "loading", "loaded" };
@@ -1165,11 +1165,11 @@ API Examples
 
 	Changes from the May 2014 CSS Font Loading Last Call Working Draft:
 
-	
      
-		
    1. 
-			Corrected the async algorithms to use "queue a task" language,
-			to ensure that side-effect timing is well-defined.
-	
    
+	1. Corrected the async algorithms to use "queue a task" language,
+		to ensure that side-effect timing is well-defined.
+
+	2. Switched {{FontFaceSetLoadEvent/fontfaces}} to be a FrozenArray,
+		to match with proper IDL practice.
 
 
    
 Acknowledgments
    
diff --git a/css-fonts/Fonts.html b/css-fonts/Fonts.html
index 61516e21468..0ddcddc9d24 100644
--- a/css-fonts/Fonts.html
+++ b/css-fonts/Fonts.html
@@ -148,6 +148,10 @@ 
    Editor's Draft
      href="https://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&product=CSS&component=Fonts&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">CSS3
      Fonts issues in Bugzilla
 
+    
    css-fonts-3
+     issues in github
+
     
    Discussion:
 
     
    [LONGSTATUS] [DATE]
    
   
    Issues List:
    
     
    CSS3 Fonts issues in Tracker
     
    CSS3 Fonts issues in Bugzilla
+    
    css-fonts-3 issues in github
   
    Discussion:
    
     
    www-style@w3.org
          with subject line “[css-fonts]
diff --git a/css-grid/Overview.bs b/css-grid/Overview.bs
index 51d32bdeba0..dcf8852ab77 100644
--- a/css-grid/Overview.bs
+++ b/css-grid/Overview.bs
@@ -34,6 +34,10 @@ At Risk: application of grid placement to absolutely-positioned boxes
 
 
     spec:css-break-3; type:dfn; text:fragment
+spec: css-flexbox-1; type:dfn
+	text: specified size
+	text: content size
+	text: transferred size
 
    
 
 
+
+
    CSS Text Decoration Level 3 Disposition of Comments for 2013-08-01 CR
    
+
+
    Dated Draft: https://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/
+
+
    Editor's Draft: http://drafts.csswg.org/css-text-decor-3/
+
+
    The following color coding convention is used for comments:
    
+
+
      
+ 
    • Accepted or Rejected and positive response
+ 
    • Rejected and no response
+ 
    • Rejected and negative response
+ 
    • Deferred
+ 
    • Out-of-Scope or Invalid and not verified
+
    
+
+
    Open issues are marked like this
    
+
+
    An issue can be closed as Accepted, OutOfScope,
+Invalid, Rejected, or Retracted.
+Verified indicates commentor's acceptance of the response.
    
+
    +Issue 1. #
+Summary:  Allow UA to skip ink by default
+From:     Edward O'Connor
+Comment:  https://www.w3.org/mid/m2iositu9t.fsf@eoconnor.apple.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0088.html
+Comment:  https://github.com/w3c/csswg-drafts/issues/727
+Changes:  None
+Open
+Resolved: =WG= Discuss.
    
+
    +Issue 2. #
+Summary:  text-decoration-color doesn't handle SVG fills
+From:     Tavmjong Bah
+Comment:  https://www.w3.org/mid/1400592192.22096.52.camel@localhost.localdomain
+Response:
+Closed:   Deferred to FXTF Paint
+Resolved: Editor discretion
    
+
    +Issue 3. #
+Summary:  Allow specifying position and thickness of underlines
+From:     Lea Verou
+Comment:  https://www.w3.org/mid/9500A3A5-957D-462D-B30C-E5C548ADEB0E@verou.me
+Response: https://www.w3.org/mid/53BE565D.5090905@inkedblade.net
+Closed:   Deferred to L4
+Resolved: [New features are deferred from CRs]
    
+
    +Issue 4. #
+Summary:  Allow arbitrary decorations
+From:     Sebastian Zartner
+Comment:  https://www.w3.org/mid/CAERejNbMCrZiBbCSRjA_1mZ3qOZyQ9PTDoH+TxvX4gp_2eSnpg@mail.gmail.com
+Response: https://www.w3.org/mid/CAAWBYDB-xMb46nMf3piNNU_fcyry0hUoKh=WfPmZma3CA=c8Gg@mail.gmail.com
+Closed:   Rejected
+Note:     Proposal is way ahead of its time; use cases may be addressed in
+          future specs, unknown as yet which ones.
+Resolved: [New features are deferred from CRs]
    
+
    +Issue 5. #
+Summary:  text-shadow should apply to inline images
+From:     Axel Dahmen
+Comment:  https://www.w3.org/mid/maatmk$bq8$1@ger.gmane.org
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0087.html
+Closed:   Rejected
+Resolved: Editor discretion
    
+
    +Issue 6. #
+Summary:  Don't underline leading/trailing spaces
+From:     Florian Rivoal
+Comment:  https://www.w3.org/mid/3A25BF98-130D-43F1-A883-90EAC8EDECB5@rivoal.net
+Response: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/2b96fce8b70457a5bb04b151833ea9de5045e6a1
+Closed:   Accepted
+Resolved: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
+Verified: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
    
+
    +Issue 7. #
+Summary:  Error in computed value of 'text-shadow'
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150326151542.GA19304@pescadero.dbaron.org
+Response: https://www.w3.org/mid/CAAWBYDB9UDyk+8v53t5kDjcTsJZJ0E8BFa5RPn3nYqh1=0VgtA@mail.gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/fe04a357105875cf26b30bf9375c8b310a517524
+Closed:   Accepted
+Resolved: Bugfix
    
+
    +Issue 8. #
+Summary:  s/above/outside/ for emphasis marks
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698Cn7Yg5+bQO8NN1YrnpZak_yXQVYRc8HUQB3OB0_x9RA@mail.gmail.com
+Response: https://www.w3.org/mid/E1CA333C-15C7-44F5-BDA1-23BBF16E5DE5@gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/a9432fa2c1e8e80418bcd30538a739854d39a7bd
+Closed:   Accepted
+Resolved: Editorial
    
+
    +Issue 9. #
+Summary:  Clarify position of emphasis marks over auto-hidden ruby
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698SXs+V8whY1vbp_bhXpX-jKa=pHK7f5xTt7XPTJh91bg@mail.gmail.com
+Response: https://www.w3.org/mid/CAN9ydbVZBG-xtm0TjTaCO4dV5ULSyZdpZJhwibYS7miBpiTUeg@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0116.html
+Open:     Waiting on Murakami-san to respond with advice.
+Resolved: =WG= Discuss.
    
+
    +Issue 10. #
+Summary:  Clarify whether emphasis marks are upright or sideways for sideways-rl/lr
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq69-O+qeoZ+_6=8ToxHuGphU1AgzcoLpHj-iKWCduKHL7Yg@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0089.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/aa9ae9847dcff26d80f2b4d097e0f13781f25a44
+Open:     Accepted
+Resolved: =WG= Review.
    
+
    +Issue 11. #
+Summary:  UA rules for text-emphasis-position should handle Japanese within Chinese
+From:     Xidorn Quan
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015Nov/0311.html
+Response: https://www.w3.org/mid/5654DED1.8070706@inkedblade.net
+Changes:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Closed:   Accepted
+Resolved: =WG= =i18n= Review.
    
+
    +Issue 12. #
+Summary:  Are there emphasis mark position preferences for Korean?
+From:     fantasai
+Comment:  https://www.w3.org/mid/5654DED1.8070706@inkedblade.net
+Open
+Resoved:  =i18n= Figure this out.
    
+
    +Issue 13. #
+Summary:  Should emphasis marks use 'font-variant: ruby'?
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq69_efU_tobZe8VDYfM9qCm0ejpiajmmys5JW4h8=oAx4Lg@mail.gmail.com
+Comment:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0111.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/22ed0ceb4192652bcee96c139326acb742b1d868
+Open:     Accepted
+Resolved: =WG= Review.
    
+
    +Issue 14. #
+Summary:  'text-emphasis' shorthand should not allow only <color>
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq699grzUvrZHMHW17bFCE-CamQmfeGgOHN-tB4ViKsWtqTA@mail.gmail.com
+Response: https://www.w3.org/mid/CAMdq699ztveczAWh1nYZekBoNFUKVz2LCiUUigUSuxV+CuT6HA@mail.gmail.com
+Closed:   Rejected
+Resolved: Editor discretion (based on existing CSS syntactic precedents)
    
+
    +Issue 15. #
+Summary:  Emphasis marks per typographic character unit
+From:     Richard Ishida
+Comment:  https://www.w3.org/mid/5652E04D.6080408@w3.org
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0084.html
+Open:     Accepted (waiting for css-text-3 publication update)
+Resolved: Editorial
    
+
    +Issue 16. #
+Summary:  Emphasis marks shouldn't apply to punctuation
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq699v=qhkpXD8smpV0TSOW_GEt67Z4HZWmTheqhv2n+=ekw@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0083.html
+Followup: https://github.com/w3c/csswg-drafts/issues/839
+Open:     =WG= =i18n= Discuss.
    
+
    +Issue 17. #
+Summary:  'text-emphasis-position' requires too many arguments
+From:     Momdo Nakamura
+Comment:  https://www.w3.org/mid/20151215203411.4682.EDA4FE4B@gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0118.html
+Open:     =WG= Discuss proposal. =i18n= Verify assumptions in proposal.
    
+
    +Issue 18. #
+Summary:  'text-underline-position' should default to 'auto' for CJK, to avoid compat issues
+From:     Masayuki Nakano
+Comment:  https://www.w3.org/mid/55506D67.7060308@d-toybox.com
+Comment:  https://www.w3.org/mid/5C756B1C-F03B-4CA7-8796-7A6EEBC34C32@apple.com
+Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0144.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/c7ca2e5cf82ddb73a8e58484eeee21750fd32d2e
+Open:     =WG= Review changes, decide whether 'text-underline-position: right' should also default to 'auto'.
    
+
    +Issue 19. #
+Summary:  'text-underline-position' UA rules don't handle non-CJK inside CJK
+From:     Myles Maxfield
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015Jun/0210.html
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0092.html
+Changes:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Closed:   Accepted
+Resolved: Bugfix
    
+
    +Issue 20. #
+Summary:  Module needs update to handle new sideways-lr/sideways-rl writing modes
+From:     fantasai
+Comment:  http://www.w3.org/mid/56E86D82.10606@inkedblade.net
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0119.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/aa9ae9847dcff26d80f2b4d097e0f13781f25a44
+Closed:   Accepted
+Resolved: =WG= =i18n= Review.
    
+
    +Issue 21. #
+Summary:  Specify interaction of text-decoration, text-emphasis, and ruby
+From:     Momdo Nakamura
+Comment:  https://www.w3.org/mid/CAMdq698GTMUd=OBrgaFLcNYWhMdmOtaYa6D-8OrGSbxZZDaibw@mail.gmail.com
+Comment:  https://github.com/w3c/csswg-drafts/issues/160
+Changes:  https://github.com/w3c/csswg-drafts/commit/f205ff9dc6b969d015aa37c710b32d3845f137c9
+Open:     =WG= =i18n= Review.
    
+
    +Issue 22. #
+Summary:  CJK vs. skipping ink
+From:     Koji Ishii
+Comment:  https://github.com/w3c/csswg-drafts/issues/707
+Open:     =WG= Discuss.
    
+
    +Issue 23. #
+Summary:  ???
+Comment:  https://github.com/w3c/csswg-drafts/issues/799
+Duplicate of 24?
    
+
    +Issue 24. #
+Summary:  line-throughs vs. skipping ink
+From:     Xidorn Quan
+Comment:  https://github.com/w3c/csswg-drafts/issues/711
+Response: https://github.com/w3c/csswg-drafts/issues/711#issuecomment-268594411
+Changes:  https://github.com/w3c/csswg-drafts/commit/6d37258d4696972886a18f2298488cf94800060a
+Closed:   Accepted
+Resolved: https://www.w3.org/mid/CADhPm3vcLHbfAhsZi8OCT+kuQOuxt_qH4rimVTewkvNR=SUi=Q@mail.gmail.com
    
+
    +Issue 25. #
+Summary:  Position of underline should depend on skipped things
+From:     Dave Hyatt
+Comment:  https://www.w3.org/mid/3ADFB47B-FE63-4820-A602-D3BABFF6126F@apple.com
+Open:     =WG= Discuss.
    
+
    +Issue 26. #
+Summary:  text-decoration-skip should have keyword for complex initial value
+From:     Florian Rivoal
+Comment:  https://github.com/w3c/csswg-drafts/issues/727
+Open:     =WG= Discuss.
    
+
    +Issue 27. #
+Summary:  underline-becoming-line-through note is confusing
+From:     Hiroshi Sakakibara
+Comment:  https://github.com/w3c/csswg-drafts/issues/160#issuecomment-224203512
+Response: https://github.com/w3c/csswg-drafts/issues/160#issuecomment-269328826
+Changes:  https://github.com/w3c/csswg-drafts/commit/0ff76a5ed7ce0e6de7c17ec4b7a357f56fcab3f0
+Closed:   Accepted
+Resolved: =WG= Discuss.
    
+
diff --git a/css-text-decor/issues-cr-2013.txt b/css-text-decor/issues-cr-2013.txt
new file mode 100644
index 00000000000..5f347b1ec98
--- /dev/null
+++ b/css-text-decor/issues-cr-2013.txt
@@ -0,0 +1,229 @@
+Draft:    https://www.w3.org/TR/2013/CR-css-text-decor-3-20130801/
+Title:    CSS Text Decoration Level 3
+
+Figure out situation for https://lists.w3.org/Archives/Public/www-style/2016Dec/0082.html ?
+
+----
+Issue 1.
+Summary:  Allow UA to skip ink by default
+From:     Edward O'Connor
+Comment:  https://www.w3.org/mid/m2iositu9t.fsf@eoconnor.apple.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0088.html
+Comment:  https://github.com/w3c/csswg-drafts/issues/727
+Changes:  None
+Open
+Resolved: =WG= Discuss.
+----
+Issue 2.
+Summary:  text-decoration-color doesn't handle SVG fills
+From:     Tavmjong Bah
+Comment:  https://www.w3.org/mid/1400592192.22096.52.camel@localhost.localdomain
+Response:
+Closed:   Deferred to FXTF Paint
+Resolved: Editor discretion
+----
+Issue 3.
+Summary:  Allow specifying position and thickness of underlines
+From:     Lea Verou
+Comment:  https://www.w3.org/mid/9500A3A5-957D-462D-B30C-E5C548ADEB0E@verou.me
+Response: https://www.w3.org/mid/53BE565D.5090905@inkedblade.net
+Closed:   Deferred to L4
+Resolved: [New features are deferred from CRs]
+----
+Issue 4.
+Summary:  Allow arbitrary decorations
+From:     Sebastian Zartner
+Comment:  https://www.w3.org/mid/CAERejNbMCrZiBbCSRjA_1mZ3qOZyQ9PTDoH+TxvX4gp_2eSnpg@mail.gmail.com
+Response: https://www.w3.org/mid/CAAWBYDB-xMb46nMf3piNNU_fcyry0hUoKh=WfPmZma3CA=c8Gg@mail.gmail.com
+Closed:   Rejected
+Note:     Proposal is way ahead of its time; use cases may be addressed in
+          future specs, unknown as yet which ones.
+Resolved: [New features are deferred from CRs]
+----
+Issue 5.
+Summary:  text-shadow should apply to inline images
+From:     Axel Dahmen
+Comment:  https://www.w3.org/mid/maatmk$bq8$1@ger.gmane.org
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0087.html
+Closed:   Rejected
+Resolved: Editor discretion
+----
+Issue 6.
+Summary:  Don't underline leading/trailing spaces
+From:     Florian Rivoal
+Comment:  https://www.w3.org/mid/3A25BF98-130D-43F1-A883-90EAC8EDECB5@rivoal.net
+Response: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/2b96fce8b70457a5bb04b151833ea9de5045e6a1
+Closed:   Accepted
+Resolved: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
+Verified: https://www.w3.org/mid/CADhPm3u5pTm7eTDQ-skjhfMA6nfHSewvnrtoYOxXVSj22HxXKw@mail.gmail.com
+----
+Issue 7.
+Summary:  Error in computed value of 'text-shadow'
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150326151542.GA19304@pescadero.dbaron.org
+Response: https://www.w3.org/mid/CAAWBYDB9UDyk+8v53t5kDjcTsJZJ0E8BFa5RPn3nYqh1=0VgtA@mail.gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/fe04a357105875cf26b30bf9375c8b310a517524
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 8.
+Summary:  s/above/outside/ for emphasis marks
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698Cn7Yg5+bQO8NN1YrnpZak_yXQVYRc8HUQB3OB0_x9RA@mail.gmail.com
+Response: https://www.w3.org/mid/E1CA333C-15C7-44F5-BDA1-23BBF16E5DE5@gmail.com
+Changes:  https://github.com/w3c/csswg-drafts/commit/a9432fa2c1e8e80418bcd30538a739854d39a7bd
+Closed:   Accepted
+Resolved: Editorial
+----
+Issue 9.
+Summary:  Clarify position of emphasis marks over auto-hidden ruby
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698SXs+V8whY1vbp_bhXpX-jKa=pHK7f5xTt7XPTJh91bg@mail.gmail.com
+Response: https://www.w3.org/mid/CAN9ydbVZBG-xtm0TjTaCO4dV5ULSyZdpZJhwibYS7miBpiTUeg@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0116.html
+Open:     Waiting on Murakami-san to respond with advice.
+Resolved: =WG= Discuss.
+----
+Issue 10.
+Summary:  Clarify whether emphasis marks are upright or sideways for sideways-rl/lr
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq69-O+qeoZ+_6=8ToxHuGphU1AgzcoLpHj-iKWCduKHL7Yg@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0089.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/aa9ae9847dcff26d80f2b4d097e0f13781f25a44
+Open:     Accepted
+Resolved: =WG= Review.
+----
+Issue 11.
+Summary:  UA rules for text-emphasis-position should handle Japanese within Chinese
+From:     Xidorn Quan
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015Nov/0311.html
+Response: https://www.w3.org/mid/5654DED1.8070706@inkedblade.net
+Changes:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Closed:   Accepted
+Resolved: =WG= =i18n= Review.
+----
+Issue 12.
+Summary:  Are there emphasis mark position preferences for Korean?
+From:     fantasai
+Comment:  https://www.w3.org/mid/5654DED1.8070706@inkedblade.net
+Open
+Resoved:  =i18n= Figure this out.
+----
+Issue 13.
+Summary:  Should emphasis marks use 'font-variant: ruby'?
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq69_efU_tobZe8VDYfM9qCm0ejpiajmmys5JW4h8=oAx4Lg@mail.gmail.com
+Comment:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0111.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/22ed0ceb4192652bcee96c139326acb742b1d868
+Open:     Accepted
+Resolved: =WG= Review.
+----
+Issue 14.
+Summary:  'text-emphasis' shorthand should not allow only 
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq699grzUvrZHMHW17bFCE-CamQmfeGgOHN-tB4ViKsWtqTA@mail.gmail.com
+Response: https://www.w3.org/mid/CAMdq699ztveczAWh1nYZekBoNFUKVz2LCiUUigUSuxV+CuT6HA@mail.gmail.com
+Closed:   Rejected
+Resolved: Editor discretion (based on existing CSS syntactic precedents)
+----
+Issue 15.
+Summary:  Emphasis marks per typographic character unit
+From:     Richard Ishida
+Comment:  https://www.w3.org/mid/5652E04D.6080408@w3.org
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0084.html
+Open:     Accepted (waiting for css-text-3 publication update)
+Resolved: Editorial
+----
+Issue 16.
+Summary:  Emphasis marks shouldn't apply to punctuation
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq699v=qhkpXD8smpV0TSOW_GEt67Z4HZWmTheqhv2n+=ekw@mail.gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0083.html
+Followup: https://github.com/w3c/csswg-drafts/issues/839
+Open:     =WG= =i18n= Discuss.
+----
+Issue 17.
+Summary:  'text-emphasis-position' requires too many arguments
+From:     Momdo Nakamura
+Comment:  https://www.w3.org/mid/20151215203411.4682.EDA4FE4B@gmail.com
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0118.html
+Open:     =WG= Discuss proposal. =i18n= Verify assumptions in proposal.
+----
+Issue 18.
+Summary:  'text-underline-position' should default to 'auto' for CJK, to avoid compat issues
+From:     Masayuki Nakano
+Comment:  https://www.w3.org/mid/55506D67.7060308@d-toybox.com
+Comment:  https://www.w3.org/mid/5C756B1C-F03B-4CA7-8796-7A6EEBC34C32@apple.com
+Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0144.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/c7ca2e5cf82ddb73a8e58484eeee21750fd32d2e
+Open:     =WG= Review changes, decide whether 'text-underline-position: right' should also default to 'auto'.
+----
+Issue 19.
+Summary:  'text-underline-position' UA rules don't handle non-CJK inside CJK
+From:     Myles Maxfield
+Comment:  https://lists.w3.org/Archives/Public/www-style/2015Jun/0210.html
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0092.html
+Changes:  https://lists.w3.org/Archives/Public/www-style/2016Dec/0094.html
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 20.
+Summary:  Module needs update to handle new sideways-lr/sideways-rl writing modes
+From:     fantasai
+Comment:  http://www.w3.org/mid/56E86D82.10606@inkedblade.net
+Response: https://lists.w3.org/Archives/Public/www-style/2016Dec/0119.html
+Changes:  https://github.com/w3c/csswg-drafts/commit/aa9ae9847dcff26d80f2b4d097e0f13781f25a44
+Closed:   Accepted
+Resolved: =WG= =i18n= Review.
+----
+Issue 21.
+Summary:  Specify interaction of text-decoration, text-emphasis, and ruby
+From:     Momdo Nakamura
+Comment:  https://www.w3.org/mid/CAMdq698GTMUd=OBrgaFLcNYWhMdmOtaYa6D-8OrGSbxZZDaibw@mail.gmail.com
+Comment:  https://github.com/w3c/csswg-drafts/issues/160
+Changes:  https://github.com/w3c/csswg-drafts/commit/f205ff9dc6b969d015aa37c710b32d3845f137c9
+Open:     =WG= =i18n= Review.
+----
+Issue 22.
+Summary:  CJK vs. skipping ink
+From:     Koji Ishii
+Comment:  https://github.com/w3c/csswg-drafts/issues/707
+Open:     =WG= Discuss.
+----
+Issue 23.
+Summary:  ???
+Comment:  https://github.com/w3c/csswg-drafts/issues/799
+Duplicate of 24?
+----
+Issue 24.
+Summary:  line-throughs vs. skipping ink
+From:     Xidorn Quan
+Comment:  https://github.com/w3c/csswg-drafts/issues/711
+Response: https://github.com/w3c/csswg-drafts/issues/711#issuecomment-268594411
+Changes:  https://github.com/w3c/csswg-drafts/commit/6d37258d4696972886a18f2298488cf94800060a
+Closed:   Accepted
+Resolved: https://www.w3.org/mid/CADhPm3vcLHbfAhsZi8OCT+kuQOuxt_qH4rimVTewkvNR=SUi=Q@mail.gmail.com
+----
+Issue 25.
+Summary:  Position of underline should depend on skipped things
+From:     Dave Hyatt
+Comment:  https://www.w3.org/mid/3ADFB47B-FE63-4820-A602-D3BABFF6126F@apple.com
+Open:     =WG= Discuss.
+----
+Issue 26.
+Summary:  text-decoration-skip should have keyword for complex initial value
+From:     Florian Rivoal
+Comment:  https://github.com/w3c/csswg-drafts/issues/727
+Open:     =WG= Discuss.
+----
+Issue 27.
+Summary:  underline-becoming-line-through note is confusing
+From:     Hiroshi Sakakibara
+Comment:  https://github.com/w3c/csswg-drafts/issues/160#issuecomment-224203512
+Response: https://github.com/w3c/csswg-drafts/issues/160#issuecomment-269328826
+Changes:  https://github.com/w3c/csswg-drafts/commit/0ff76a5ed7ce0e6de7c17ec4b7a357f56fcab3f0
+Closed:   Accepted
+Resolved: =WG= Discuss.
+----
diff --git a/css-text/Overview.bs b/css-text/Overview.bs
index cd43358af78..82936bb17a7 100644
--- a/css-text/Overview.bs
+++ b/css-text/Overview.bs
@@ -650,16 +650,21 @@ Languages and Typesetting
    
       segment breaks are not collapsible
       and are instead transformed into a preserved line feed (U+000A).
 
-      
    For other values of 'white-space', segment breaks are collapsible,
-        and are either transformed into a space (U+0020) or removed
-        depending on the context before and after the break:
    
+      
    For other values of 'white-space', segment breaks are collapsible.
+        As with spaces,
+        any collapsible segment break immediately following another collapsible segment break
+        is removed.
+        Then the remaining segment breaks are
+        either transformed into a space (U+0020) or removed
+        depending on the context before and after the break:
 
       
      
         
    • If the character immediately before or immediately after the segment
           break is the zero-width space character (U+200B), then the break
           is removed, leaving behind the zero-width space.
         
    • Otherwise, if the East Asian Width property [[!UAX11]] of both
-          the character before and after the line feed is F, W, or H (not A),
+          the character before and after the segment break is F,
+          W, or H (not A),
           and neither side is Hangul, then the segment break is removed.
         
    • Otherwise, the segment break is converted to a space (U+0020).
       
    
diff --git a/css-transforms-2/issues-wd-2013.txt b/css-transforms-2/issues-wd-2013.txt
new file mode 100644
index 00000000000..e76657c8b36
--- /dev/null
+++ b/css-transforms-2/issues-wd-2013.txt
@@ -0,0 +1,428 @@
+Draft:    https://www.w3.org/TR/2013/WD-css-transforms-1-20131126/
+Title:    CSS Transforms Level 2
+Dates:    2012/05/01 through 2016/12/29
+
+3D Transforms Included (moved from L1 per WG resolution)
+
+Actions requiring Internet access:
+ * Make sure https://www.w3.org/Bugs/Public/show_bug.cgi?id=16328#c4  is closed
+ * File https://www.w3.org/mid/CAPeKFTj12CiGQ31iQf5A90W04vY5CaZapXdr9uFf46EmfmBr3A@mail.gmail.com as clarification issue against filters
+
+----
+Issue 1.
+Summary:  transform-style doesn't define keywords
+From:     Dirk Schulze
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=22427
+Response:
+Open:     =ED= Edit
+Resolved: Bugfix
+----
+Issue 2.
+Summary:  Undefined variable in matrix decomposition formula
+From:     Manish Goregaokar
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29815
+Response:
+Open:     =ED= Edit
+Resolved: Bugfix
+----
+Issue 3.
+Summary:  Clarify normalization to unit vector for rotate3d
+From:     Mike Taylor
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29417
+Response:
+Open:     =ED= Edit
+Resolved: Editorial
+----
+Issue 4.
+Summary:  transform properties should restrict application
+From:     Matt Rakow (ChumpChief)
+Comment:  https://github.com/w3c/csswg-drafts/issues/260
+Response: https://github.com/w3c/csswg-drafts/issues/260#issuecomment-230065135
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 4.
+Summary:  Misleading illustration/description on perspective
+From:     Alan Gresley
+Comment:  http://www.w3.org/mid/53C27AA6.2090304@css-class.com
+Open:     =ED= Edit.
+Resolved: Editorial
+----
+Issue 5.
+Summary:  Add more math to spec
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201204211540.35418.Dr.O.Hoffmann@gmx.de
+Open:     =ED= Discuss and edit as necessary.
+Resolved: Editor discretion
+----
+Issue 6.
+Summary:  Perspective origin should use 
+From:     Tab Atkins
+Comment:  http://www.w3.org/mid/CAAWBYDAsBnK94=Av3HvkeNz0wu05=3Fx3FS6fq19oVhB8T0yTQ@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAAWBYDBKLvZo9BR=ogEqZMmLZgtsFwBWB+cs43sdm=N1Bep0tg@mail.gmail.com
+Response: http://www.w3.org/mid/ECBC7E52-958A-4370-96F7-6DFB492BECC8@me.com
+Open:     Accepted =ED= Ensure remaining edits per https://www.w3.org/mid/CAAWBYDCkiz1BLP-qB6S8Pn0x=KzVoBL7Xih8GaHbX4To=2Og9w@mail.gmail.com and up-thread comments from yself
+Resolved: =WG= Discuss whether to use a  that excludes 3-value variant
+Notes:    This should have an all-WG resolution since it crosses multiple modules
+----
+Issue 7.
+Summary:  Specify handling of omitted values in scale
+from:     Shane Stephens
+Comment:  https://www.w3.org/mid/CAGTfzwRBh7ShL31THKm-4NSKMZw6M8rMmtS9VO9zMA3sqPk23Q@mail.gmail.com
+Response: https://www.w3.org/mid/55814FE8.6030003@inkedblade.net
+Comment:  https://www.w3.org/mid/CAGTfzwScjgx4FV0gC2hTW4_4T+KZvqV6Ky-5n_hDtZsjY47f_w@mail.gmail.com
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 8.
+Summary:  Possibly outstanding edits on rotate3d()
+From:     CSSWG
+Comment:  http://www.w3.org/mid/CADhPm3tF-tBQMwhOWRAYN-L+rVPhX-_xAa6ynKGa57Ue4HMywA@mail.gmail.com
+Open:     =ED= Edit.
+Resolved: http://www.w3.org/mid/CADhPm3tF-tBQMwhOWRAYN-L+rVPhX-_xAa6ynKGa57Ue4HMywA@mail.gmail.com
+----
+Issue 9.
+Summary:  Should rotate3d be listed as a primitive?
+From:     Boris Zbarsky
+Comment:  http://www.w3.org/mid/CAF-RrDuzdnEDXP=E4yo9p4kTL=4fwRoqtdpqXmfWdXbSBPWYXA@mail.gmail.com
+Response:
+Open:     =ED= Reconcile with other rotate() edits.
+Resolved: Probably bugfix, based on other WG resolutions.
+----
+Issue 10.
+Summary:  When is rotate3d() normalized?
+From:     David Baron
+Comment:  https://www.w3.org/mid/20120821212052.GA717@crum.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 11.
+Summary:  Add transform-snap property
+From:     Tim Severien
+Comment:  https://www.w3.org/mid/CALtEqHo5gWwZii6Tv0XJ=BBa=b1k+9K4ipVyuDw2YYL==36JkQ@mail.gmail.com(sfid-20140620_043734_567184_BF1C7F6C)
+Response: https://www.w3.org/mid/CAAWBYDDiQEmONwEj66Nt+Q+b=e1uCEeVs3kRw+GYHWAjQMQqnw@mail.gmail.com
+Closed:   Rejected or deferred? due to insufficient use cases
+Resolved: Editor discretion
+----
+Issue 12.
+Summary:  Add generic transform function
+From:     Axel Dahmen
+Comment:  https://www.w3.org/mid/ls0e3v$qp9$1@ger.gmane.org
+Response: https://www.w3.org/mid/C1341BA9-D798-44B4-B7F2-DE2B18D160DC@adobe.com
+Response: http://www.w3.org/mid/CAAWBYDBO227OP_T74bmkTeCR5A6U30+fegGgOeq4qEpqjUFkTA@mail.gmail.com
+Comment:  https://www.w3.org/mid/mpvaav$l5n$1@ger.gmane.org
+Open:     =WG= Discuss. (Probably to close as defer?)
+Resolved:
+----
+Issue 13.
+Summary:  SVGTransform interface sucks for 3d transforms
+From:     Patrick martin
+Comment:  https://www.w3.org/mid/CAN_rxo0tyfoLg6cPgTq2G-3Q41zTPMfemsXTXxh_ZBjeXB3vKQ@mail.gmail.com
+Open:     =WG= Discuss.
+----
+Issue 14.
+Summary:  Overuse of stacking context / containing block by perspective
+From:     David Baron
+Comment:  https://www.w3.org/mid/20140222183507.GA4235@crum.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 15.
+Summary:  Improve description of 'perspective' and 'perspective-origin'
+From:     Dean Jackson
+Comment:  https://www.w3.org/mid/121C24DC-B2C8-40AE-A40B-78F1AB3C0D5B@apple.com
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved:
+----
+Issue 16.
+Summary:  Specs disagree on whether perspective-origin's resolved value is used or computed
+From:     Xidorn Quan (usurper)
+Comment:  https://github.com/w3c/csswg-drafts/issues/392
+Proposal: https://github.com/w3c/csswg-drafts/issues/392#issuecomment-269639534
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 17.
+Summary:  perspective(0) violates open range restriction, results in non-interop
+From:     Daniel Glazman
+From:     Xidorn Quan
+Comment:  https://github.com/w3c/csswg-drafts/issues/413
+Comment:  https://www.w3.org/mid/4fec8a8e-8957-51b6-4572-39aade8c5f4a@disruptive-innovations.com
+Comment:  https://www.w3.org/mid/CAMdq69_54_c3k46rQnynr7k88_aqpRAoH3KcC+zYHac2bYCbYA@mail.gmail.com
+Response: https://www.w3.org/mid/CAAWBYDCdwyDa6Gr-xLnon_JpSafvfmRUaALJjr7g_NBLyv4tbw@mail.gmail.com
+Changes:
+Open:     =WG= Resolve.
+Resolved:
+----
+Issue 18.
+Summary:  Errors in definition of 'perspective'
+From:     David Baron
+Comment:  http://www.w3.org/mid/20140222232128.GA7570@crum.dbaron.org
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 19.
+Summary:  Bugs in interpolation algorithm
+From:     Manish Goregaokar (Manishearth)
+Comment:  https://github.com/w3c/csswg-drafts/issues/483#issuecomment-249497761
+Response:
+Changes:
+Open:     =ED= Edit or ask for help.
+Resolved: Bugfix.
+----
+Issue 20.
+Summary:  Define exactly how to apply perspective (w-parameter)
+From:     Aryeh Gregor
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=15605
+Response:
+Open:     =WG= Do something.
+Resolved:
+----
+Issue 21.
+Summary:  Should transform-style: perserve-3d contain abspos?
+From:     Simon Fraser
+Comment:  https://www.w3.org/mid/66B2D1D5-85EF-4F77-AC6D-BCF86752EC6B@me.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 22.
+Summary:  transform-style auto vs inheritance
+From:     Matt Rakow
+Comment:  https://www.w3.org/mid/028e0b56bc2842c1914428430b08341c@BL2PR03MB260.namprd03.prod.outlook.com
+Comment:  https://www.w3.org/mid/223e9280c4974ff8b292c3bec21d1861@BL2PR03MB260.namprd03.prod.outlook.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 23.
+Summary:  Definition of bounding box
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/B7126E1C-EB7C-4D9F-9238-F9CDD72BDB21@adobe.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 24.
+Summary:  opacity flattening is unwelcome (multiple-thread issue)
+From:     Joseph Orbegoso Pea (trusktr)
+From:     Matt Woodrow
+From:     Andrew Prendergast
+Comment:  http://www.w3.org/mid/CAKU1PAVwFzBi-REsG-XJp9pN9FSokRC302-fzmwAsY-42Gyfyw@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAKU1PAVHATHSfK=NziFGCYxVUTUNf3FbW9WQy+hmTJ0TNvyS9Q@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAKU1PAXZCopvkNk6_weYVqQC1HLkY-NR1rA-R6-WLPqRHVcLkQ@mail.gmail.com
+Comment:  https://github.com/w3c/csswg-drafts/issues/496
+Comment:  https://www.w3.org/mid/E119A6ACA1E659419D330C8CBF8B6B7698780555@EX2K10MBX08.secure.hosting
+Notes:    See also thread http://www.w3.org/mid/56CE6AD7.5050208@mozilla.com
+          ending at http://www.w3.org/mid/2f96a00e-cb8a-a846-e0ab-0a0f6c2f4c71@mozilla.com
+          resolved at https://www.w3.org/mid/CADhPm3vbyNNkMpi3E8xCWoQZnniuDH_zco4wy-yXysrEt5fWoQ@mail.gmail.com
+          See also thread at http://www.w3.org/mid/CAKA+AxmLh=U2o4f2WaamDH1MqxLfU6c4cqud7ktdf3eY4Q87hw@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 25.
+Summary:  Definition of 3D transform context Meta-Issue
+          because I can't untangle this without actually understanding it all
+From:     Simon Fraser
+From:     Robert O'Callahan
+From:     Matt Rakow
+From:     Tien-Ren Chen
+From:     Joseph Orbegoso Pea (trusktr)
+Comment:  https://www.w3.org/mid/CAOp6jLb+peP27eBBdYXg8J2=OfqwENhXgcZ-GX_OoF9muFJ_MA@mail.gmail.com
+Comment:  https://www.w3.org/mid/CADhPm3shMt_ubqtooOF2qkH-1cC6LZXN+q6UW0zh9yiojYeR_w@mail.gmail.com
+Comment:  https://www.w3.org/mid/BLUPR03MB135AFD98360A36799393E1FAD7B0@BLUPR03MB135.namprd03.prod.outlook.com
+Comment:  http://www.w3.org/mid/CAKxkHO8QW=D_BMC_ic2oHsnK8fF5f2NB6QXHE2LZP3GV4qTrcQ@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAKU1PAXsR=BW-929La1U9_SPmW_TJmgmkBGkcoEFX6GXOBvMhQ@mail.gmail.com
+Notes:    This is a bunch of issues & review requests that probably need untangling.
+Open:     =WG= Review and discuss (but review first so y'all not repeating y'selves)
+----
+Issue 26.
+Summary:  “accumulated 3D transformation matrix” is misleading
+From:     Dean Jackson
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17433
+Response:
+Open:     =dino= Propose edits.
+Resolved: Editorial?
+----
+Issue 27.
+Summary:  Define mapping from 3d rendering context to document
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/D89A82DF-BFA4-42D5-AD8E-9EE171E85582@adobe.com
+Response:
+Open
+----
+Issue 28.
+Summary:  Clarify which elements participate in 3d rendering context
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150904234027.GA15075@pescadero.dbaron.org
+Response:
+Open
+Resolved: Editorial
+----
+Issue 29.
+Summary:  Clarify which elements establish 3d rendering context
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150904234027.GA15075@pescadero.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 30.
+Summary:  Clarify interaction of preserve-3d and backface-visibility
+From:     Shawn Singh
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=23015
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 31.
+Summary:  Can't test backface-visibility
+From:     Shawn Singh
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=23014
+Response:
+Open:     =WG= Discuss for ideas or close no action.
+Resolved:
+----
+Issue 32.
+Summary:  Rendering descendent content of backface-visibility: hidden
+From:     Matt Rakow
+Comment:  https://www.w3.org/mid/BY2PR03MB361F3742C5D1619AD252055AD1F0@BY2PR03MB361.namprd03.prod.outlook.com
+Proposal: https://www.w3.org/mid/BY2PR03MB3618D80171E55B6954870AAAD180@BY2PR03MB361.namprd03.prod.outlook.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 33.
+Summary:  Overflow clipping should not always create stacking context
+From:     Tien-Ren Chen
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28252
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 34.
+Summary:  ??????????????????????????
+From:     Robert O'Callahan
+Comment:  https://www.w3.org/mid/CAOp6jLaVRqpdpMdkem4LKtaX5dJ+SKhqjMW4jShX2ub9tBCacg@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 35.
+Summary:  Impact of perspective transforms on scrollable area
+From:     Matt Woodrow
+Comment:  https://www.w3.org/mid/56415511.5090604@mozilla.com
+Response: https://www.w3.org/mid/2DEAB33D-69E9-475A-B29D-805BA3C9ACEF@me.com
+Notes:    See also related issue in L1
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 36.
+Summary:  Should backface-visibility create a stacking context?
+From:     Philip Rogers
+Comment:  http://www.w3.org/mid/CAJgFLLuRnYT2Pk_At9Td-DxvOUUW5we5S1Tgc9wYoXitct-1XA@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAJgFLLtj5hWYCNT5dHO_9WKxbn2xytV_FtO1wH-Q-Qi5VfmdGg@mail.gmail.com
+Response:
+Open
+Resolved:
+----
+Issue 37.
+Summary:  Which descendants does backface-visibility affect?
+From:     Philip Rogers
+Comment:  http://www.w3.org/mid/CAJgFLLtj5hWYCNT5dHO_9WKxbn2xytV_FtO1wH-Q-Qi5VfmdGg@mail.gmail.com
+Response:
+Open
+Resolved:
+----
+Issue 38.
+Summary:  backface-visiblity vs isolated groups like compositing/blending
+From:     Philip Rogers
+Comment:  http://www.w3.org/mid/CAJgFLLtj5hWYCNT5dHO_9WKxbn2xytV_FtO1wH-Q-Qi5VfmdGg@mail.gmail.com
+Response:
+Open
+Resolved:
+----
+Issue 39.
+Summary:  Clarify which elements affected by 'backface-visibility: hidden'
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150904234027.GA15075@pescadero.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 40.
+Summary:  Clarify Appendix E rendering of 3D transformed descendants
+From:     David Baron
+Comment:  http://www.w3.org/mid/20150904234527.GA15137@pescadero.dbaron.org
+Response:
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 41.
+Summary:  non-scaling stroke vs 3D transforms
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/CF58362A-529B-4ADE-B084-6FD320557FB8@adobe.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 42.
+Summary:  Rendering transforms with non-invertible matrix
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201204221814.06054.Dr.O.Hoffmann@gmx.de
+Response:
+Open:     ??
+Resolved:
+----
+Issue 43.
+Summary:  Add translate/rotate/scale as properties
+From:     Tab Atkins
+Comment:  https://www.w3.org/mid/CAAWBYDA16Eq9OSWTAmsxVCi0aUt3VWeS9iE54BZyRpP9Qu4v7Q@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAAWBYDBb3BefrFF-EqnCL_hqioOEn235quEt_ACtA3H+H5iOUA@mail.gmail.com
+Response:
+Closed:   Accepted
+Resolved: http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com
+----
+Issue 44.
+Summary:  Origins for translate/rotate/scale
+From:     David Baron
+From:     fantasai
+Comment:  https://www.w3.org/mid/20140806163820.GA9707@crum.dbaron.org
+Comment:  https://www.w3.org/mid/53C38564.8000801@inkedblade.net
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 45.
+Summary:  Wrong computed values for translate/rotate/scale
+From:     David Baron
+Comment:  https://www.w3.org/mid/20150924081528.GA505@pescadero.dbaron.org
+Response: https://www.w3.org/mid/CADhPm3svAZA3pMv3c9EjQCifXW8zgrxgyNBxCt9PEpOYias4Bg@mail.gmail.com
+Open:     =ED= Edit if still necessary, and close as Accepted.
+Resolved: Bugfix
+----
+Issue 46.
+Summary:  Get rid of @media transform features
+From:     Bogdan Brinza
+Comment:  http://www.w3.org/mid/e7838e6a530e418f86fde470b38eeec0@BLUPR03MB133.namprd03.prod.outlook.com
+Response: https://www.w3.org/mid/CAAWBYDCLsYTBRVz+07OJjohhKfupTVNy18hnQ8rApp90tBWKRw@mail.gmail.com
+Open:     =WG= Follow up.
+Resolved: Out-of-Scope
+----
+Issue 47.
+Summary:  Expand transform-origin to take a list
+From:     Sebastian Zartner (SebastianZ)
+Comment:  https://github.com/w3c/csswg-drafts/issues/589
+Response:
+Open:     =WG= Dicuss.
+Resolved:
+----
diff --git a/css-transforms/issues-wd-2013.html b/css-transforms/issues-wd-2013.html
new file mode 100644
index 00000000000..ca057fa0520
--- /dev/null
+++ b/css-transforms/issues-wd-2013.html
@@ -0,0 +1,567 @@
+
+
+CSS Transforms Level 1 Disposition of Comments for 2013-11-26 WD
+
+
+
    CSS Transforms Level 1 Disposition of Comments for 2013-11-26 WD
    
+
+
    Dated Draft: https://www.w3.org/TR/2013/WD-css-transforms-1-20131126/
+
+
    Editor's Draft: http://drafts.csswg.org/css-transforms-1/
+
+
    The following color coding convention is used for comments:
    
+
+
      
+ 
    • Accepted or Rejected and positive response
+ 
    • Rejected and no response
+ 
    • Rejected and negative response
+ 
    • Deferred
+ 
    • Out-of-Scope or Invalid and not verified
+
    
+
+
    Open issues are marked like this
    
+
+
    An issue can be closed as Accepted, OutOfScope,
+Invalid, Rejected, or Retracted.
+Verified indicates commentor's acceptance of the response.
    
+
    +Issue 1. #
+Summary:  Issues list link is outdated
+From:     Rick Byers
+Comment:  https://github.com/w3c/csswg-drafts/issues/486
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial
    
+
    +Issue 2. #
+Summary:  Add more info to “Module Interactions”
+From:     Dirk Schulze
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17237
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial
    
+
    +Issue 3. #
+Summary:  Convert to <*-percentage> notation
+From:     Sebastian Zartner (SebastianZ)
+Comment:  https://github.com/w3c/csswg-drafts/issues/645
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial.
    
+
    +Issue 4. #
+Summary:  Define transform list using grammar
+From:     Sebastian Zartner
+Comment:  https://www.w3.org/mid/CAERejNZgyWKV5ioh3KR9BmYYrvpM5919D9z1Qb-LjQ5zBGOFuQ@mail.gmail.com
+Response: http://www.w3.org/mid/CAAWBYDCB7nP+rqj7DzAef6zqMHtvoshLGMJuL7PsMi-V9qvPfw@mail.gmail.com
+Closed:   Invalid
    
+
    +Issue 5. #
+Summary:  Clarify matrix index convention
+From:     Maurizio Casimirri
+Comment:  http://www.w3.org/mid/C73D086A-A220-48E3-A3DC-6195D350C3FA@gmail.com
+Open:     =ED= Edit.
+Resolved: Editorial
    
+
    +Issue 6. #
+Summary:  Confusion about multiplication
+From:     Simon Sapin & Boris Zbarsky
+Comment:  https://www.w3.org/mid/509FCC62.5080101@mit.edu
+Response:
+Open:     =ED= Make sure comments in thread are all addressed
+Resolved: Bugfix
    
+
    +Issue 7. #
+Summary:  Application of transform to inlines
+From:     Gérard Talbot
+Comment:  https://www.w3.org/mid/b464220dd959f9a9f808dd4aad85288e@gtalbot.org
+Comment:  http://www.w3.org/mid/20140210195906.GA18205@crum.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 8. #
+Summary:  Computed Style of 'transform'
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/A020C5AD-51B0-4288-8D8A-9D8322213D5B@adobe.com
+Comment:  http://www.w3.org/mid/20140325212945.GA26872@crum.dbaron.org
+Response: http://www.w3.org/mid/314879EA-CF63-4792-90DD-36000224B04F@adobe.com
+Open:     =ED= Verify if fixed, else edit.
+Resolved: Bugfix
+Verified: [need a response where dbaron says it's all good now]
    
+
    +Issue 9. #
+Summary:  Error in order of multiple transform function
+From:     rosenau
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29110
+Response:
+Open:     =ED= Edit.
+Resolved: Bugfix
    
+
    +Issue 10. #
+Summary:  Clarify behavior for gradientTransform and patternTransform
+From:     Erik Dahlström
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=26470
+Response:
+Open:     =Dirk= Deal. or =WG= Discuss.
    
+
    +Issue 11. #
+Summary:  Use of “containing block” does not match CSS2.1 definition
+From:     Aryeh Gregor
+From:     Simon Sapin
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=16328
+Comment:  http://www.w3.org/mid/514E058C.5060105@exyr.org
+Response:
+Notes:    See also dbaron's message in the issue below.
+Open:     =ED= Figure out what to do.
+Resolved: Editor discretion (or agenda+ if there's a problem)
    
+
    +Issue 12. #
+Summary:  Spec doesn't mention establishing abspos containing block
+From:     Robert O'Callahan
+Comment:  https://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com
+From:     David Baron
+Comment:  https://www.w3.org/mid/20151125002414.GA22745@pescadero.dbaron.org
+Response:
+Open:     =ED= Edit.
+Resolved: Bugfix
    
+
    +Issue 13. #
+Summary:  Interaction of regions and transforms and abspos/fixedpos
+From:     Mihnea-Vlad Ovidenie
+Comment:  https://www.w3.org/mid/CE4E28E9.4B01C%25mihnea@adobe.com
+Response: =astearns= File against Regions
+Closed:   Out-of-Scope
    
+
    +Issue 14. #
+Summeray: Specify stack level of non-positioned transformed elements
+From:     Øyvind Stenhaug
+Comment:  http://www.w3.org/mid/op.wg8psjr1bunlto@oyvinds-desktop
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Bugfix
    
+
    +Issue 15. #
+Summary:  Clarify Appendix E rendering of 2D transformed descendants
+From:     David Baron
+Comment:  http://www.w3.org/mid/20150904234527.GA15137@pescadero.dbaron.org
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Bugfix
    
+
    +Issue 16. #
+Summary:  transform functions should accept percentages
+From:     Boris Zbarsky
+Comment:  https://www.w3.org/mid/546F5D45.6030704@mit.edu
+Response: https://www.w3.org/mid/A2D81F68-B51F-468C-8C10-50D435980254@adobe.com
+Closed:   Accepted
+Resolved: Bugfix
    
+
    +Issue 17. #
+Summary:  Define basis for percentage transform on patterns, gradients, clipPath
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/9B0DDCB4-B480-471F-943A-C5ED00598DFA@adobe.com
+Changes:
+Open:     =WG= Discuss.
    
+
    +Issue 18. #
+Summary:  Match SVG spec for interaction with object bounding box units
+From:     Amelia Bellamy-Royds
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28385
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Editor discretion.
    
+
    +Issue 19. #
+Summary:  Update “transformable elements” for SVG2
+From:     Nikos Andronikos
+Comment:  https://github.com/w3c/csswg-drafts/issues/358
+Response:
+Changes:
+Open:     =ED= Edit
+Resolved: Editor discretion
    
+
    +Issue 20. #
+Summary:  Units aren't back-compatible with old SVG
+From:     Dr. Olaf Hoffman
+Comment:  https://www.w3.org/mid/201204211629.13408.Dr.O.Hoffmann@gmx.de
+Response: https://www.w3.org/mid/3DCACD7B-0115-44FC-901A-A86DC1211CD1@adobe.com
+Closed:   Rejected
+Resolved: Editor discretion
    
+
    +Issue 21. #
+Summary:  Unitless values
+From:     Tab Atkins
+Comment:  http://www.w3.org/mid/CAAWBYDDDDMY0czypkLQ2X8tBtLFjYn5t9g+aYOPBzXLEAGzBzA@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAAWBYDD3VfCvDfe0TEUJEd7e+JXZzhRDGTyEgdc9Hodz0pCLUQ@mail.gmail.com
+Open:     =ED= Edit.
+Resolved: =WG= Resolve.
    
+
    +Issue 22. #
+Summary:  Transform syntax CSS vs SVG harmonization
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/7E680372-9199-4AF9-98A1-C7B6ECB72C87@adobe.com
+Response: https://www.w3.org/mid/88568E75-27C9-4DA4-BCD6-7459FA5D9FE4@adobe.com
+Open:     Accepted
+Resolved: =WG= Review.
    
+
    +Issue 23. #
+Summary:  User coordinate space statement breaks SVG
+From:     Amelia Bellamy-Royds
+Comment:  http://www.w3.org/mid/CAFDDJ7yhF7Qn28wVMqb7ra6N9Q=j74OTqHWpjLeYrH=LQwmd4A@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
    
+
    +Issue 24. #
+Summary:  Issues with transform on SVG root
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/0A9D2705-9FFE-425B-B3CB-297EA97D337D@adobe.com
+Open:     =SVGWG= Figure out if anything remains to be done.
    
+
    +Issue 25. #
+Summary:  Transforms on root SVG element
+From:     Amelia Bellamy-Royds
+Comment:  http://www.w3.org/mid/CAFDDJ7xQp+j2c+18zkRyPWPtnuk+dbVA6Dc_L7ACr-tptAGicA@mail.gmail.com
+Response:
+Open:     =WG= Discuss with SVG folks
    
+
    +Issue 26. #
+Summary:  Use UA style sheet instead of prose for SVG transform-origin
+From:     Dirk Schulze
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28000
+Comment:  https://www.w3.org/mid/20150611085235.GA3929@wok.mcc.id.au
+Response: https://www.w3.org/mid/CE3AFDB0-D260-493A-9110-16BB01D8E28E@adobe.com
+Open:     =ED= Edit.
+Resolved: Editor discretion
    
+
    +Issue 27. #
+Summary:  Specs disagree on whether transform-origin's resolved value is used or computed
+From:     Xidorn Quan
+Comment:  https://github.com/w3c/csswg-drafts/issues/392#issuecomment-238494067
+Proposal: https://github.com/w3c/csswg-drafts/issues/392#issuecomment-269639534
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 28. #
+Summary:  transform-origin relative to containing block
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698_DMux4CFD6pA2MOdK7VX9yCWJgciXE0_MuRxXAV1WMA@mail.gmail.com
+Response: https://www.w3.org/mid/CAMdq698unKqMTgJpVXFmRtcmcjfwEkhGfmhhk0dsZgxiQ4E6uQ@mail.gmail.com
+Closed:   Retracted
    
+
    +Issue 29. #
+Summary:  Add transform-origin-x/y?
+From:     Boris Zbarsky
+Comment:  https://www.w3.org/mid/50648288.4050309@mit.edu
+Response:
+Note:     CSS Backgrounds L4 solved the logical coords problem
+          since this thread was last discussed.
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 30. #
+Summary:  transform-origin: 0% not equivalent to 0px is confusing
+From:     Cameron McCormack
+Comment:  https://www.w3.org/mid/525F2287.8050002@mcc.id.au
+Response:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 31. #
+Summary:  exact definition of origin argument to rotate()
+From:     Rik Cabanier
+Comment:  http://www.w3.org/mid/CAGN7qDC=oAU5XQt0E7sJ=2vcMLU1BzmH4L7EzYsfvtL-5LbHZQ@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAKA+Axk=-C3tTdoKRU3g2Be=GV3aeiNfqYot3205h6fZVP2K=w@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAGN7qDD9LftfaCqnH_oPXe78GqYv2aOdE8forTWN515=-UHRmg@mail.gmail.com
+Proposal: http://www.w3.org/mid/CAGN7qDAw3eU72K-QSeMVmqPjh0_wihnBf7rG4bsVsQnfVSDJ5g@mail.gmail.com
+Changes:  [link to relevant section(s)]
+Open:     =ED= Needs edits?
+Resolved: =WG= Discuss.
    
+
    +Issue 32. #
+Summary:  Unitless zero rotation
+From:     Simon Fraser
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29413
+Response:
+Open:     =ED= Update to reference CSS Values 3 correctly?
+Resolved: [Sydney F2F 2016? need to find minutes]
    
+
    +Issue 33. #
+Summary:  Make Rotation Less Weird
+From:     Shane Stephens
+Comment:  https://www.w3.org/mid/CAGTfzwT8M0_c1Wnk5To1zRVtGXtuLzXbjkpDS55DC6T9dUTfKQ@mail.gmail.com
+Notes:    See also zero-coord axis issue below.
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 34. #
+Summary:  Reduce matrix decomposition when rotation axis has zero coord
+From:     Shane Stephens
+Comment:  http://www.w3.org/mid/CAGTfzwTS9r+z1LRu=3t25NW0A6yk0b+agaH6__8ZkcSD3-LR9A@mail.gmail.com
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 35. #
+Summary:  Interpolation of transform lists
+From:     David Baron
+Comment:  http://www.w3.org/mid/20120719213826.GA8775@crum.dbaron.org
+Response: http://www.w3.org/mid/474B73CD-95F5-467B-9F39-90D7045E3A9C@adobe.com
+Closed:   Accepted
+Resolved: ?
+Verified: [get verification from dbaron]
    
+
    +Issue 36. #
+Summary:  Add null transform as placeholder for animations?
+From:     CSSWG
+Comment:  http://www.w3.org/mid/523AB5BE.50406@inkedblade.net
+Response:
+Open:     =WG= Discuss or defer.
+Resolved:
    
+
    +Issue .37
+Summary:  Smarter interpolation of truncated transform lists
+From:     Louis-Rémi Babé
+Comment:  https://www.w3.org/mid/CALXxKfCKZd+P0mH2oFyDkBgps56WqwQnLSMpKk1nrqiFXScqVA@mail.gmail.com
+Response: https://www.w3.org/mid/CAAWBYDBPafEbiXNy=Mw4a9w1jmvK6dUJzq28PPjN7APgtjqAEw@mail.gmail.com
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 38. #
+Summary:  Transform interpolation problem
+From:     David Baron
+Comment:  https://www.w3.org/mid/20140702002134.GA26687@crum.dbaron.org
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 39. #
+Summary:  Interpolated values don't interpolate well with original start/end
+From:     David Baron
+Comment:  https://www.w3.org/mid/20140226234818.GA5390@crum.dbaron.org
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 40. #
+Summary:  Bugs in interpolation algorithm
+From:     Manish Goregaokar (Manishearth)
+Comment:  https://github.com/w3c/csswg-drafts/issues/483#issuecomment-249497761
+Response:
+Changes:
+Open:     =ED= Edit or ask for help.
+Resolved: Bugfix.
    
+
    +Issue 41. #
+Summary:  Matrix Interpolation
+From:     Shane Stephens
+Comment:  http://www.w3.org/mid/CADhPm3tF-tBQMwhOWRAYN-L+rVPhX-_xAa6ynKGa57Ue4HMywA@mail.gmail.com
+Notes:    Might be further background elsewhere, didn't find it. But see below.
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 42. #
+Summary:  Use better matrix interpolation method
+From:     Ken Shoemake
+From:     Benoit Jacob
+Comment:  http://www.w3.org/mid/52CD882F.6020408@yahoo.com
+Comment:  http://www.w3.org/mid/CAJTmd9qXg+WAt5OK9g-pTEwHunEXxcKtvBSJ4fd_5=SmLHM-jg@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 43. #
+Summary:  Matrix Decomposition
+From:     Dirk Schulze
+From:     Rik Cabanier
+Comment:  https://www.w3.org/mid/A54A72B2-5BFB-46F7-8B08-BE2B7A3EA8D2@adobe.com
+Comment:  http://www.w3.org/mid/CAGN7qDBdtR1AWowudWzrj0ownknbvatv-HhC1E28_QJYSB47aQ@mail.gmail.com
+Open:     =WG= Discuss.
+Resolved:
    
+
    +Issue 44. #
+Summary:  Include Tagaki-san's definition of linear scale
+From:     CSSWG
+Comment:  http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com
+Open:     =ED= Edit.
+Resolved: http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com
    
+
    +Issue 45. #
+Summary:  getTransformToElement needs more detail
+From:     CSSWG
+Comment:  https://www.w3.org/mid/CADhPm3t+PxH+eCXcOxiX61J_Nx+jimkttsoViSCQNDSVOTKNDQ@mail.gmail.com
+Response:
+Changes:
+Open:     Needs proposed text.
+Resolved:
    
+
    +Issue 46. #
+Summary:  transform-box values & correspondance to SVG vs CSS
+From:     Erik Dahlström
+Comment:  https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain
+Response:
+Notes:    See also https://drafts.fxtf.org/paint/#fill-origin
+Open:     =WG= Discuss, and ensure alignment with FXTF Paint.
+Resolved:
+Notes:    This should have an all-WG resolution since it crosses multiple modules
    
+
    +Issue 47. #
+Summary:  Scrollbars vs. scaling down
+From:     Tab Atkins
+Comment:  https://www.w3.org/mid/CAAWBYDDX2ECLHm523xNpr8qqYgsqeU2SXiY0GvZo7S1063CoAg@mail.gmail.com
+Response: https://www.w3.org/mid/CAOp6jLYZ8VMPW4wNOMkH_uLPROr1ows22AFgLqMuhzQ=h89m0A@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAAWBYDDfy0ghxEB5jnSTP3LMTbGo1=p=Wq5GUizw3RySS6QGJA@mail.gmail.com
+Response: https://www.w3.org/mid/CAOp6jLYTvsqEYfUv=mfayYADuJnZKhC1vakfdqsFvrPu0Tp_7A@mail.gmail.com
+Closed:   Invalid
+Verified: =ED= Verify.
    
+
    +Issue 48. #
+Summary:  Impact of transforms on scrollable area (multiple threads)
+From:     Robert O'Callahan
+Comment:  http://www.w3.org/mid/CAOp6jLbN9SjQd4zRy=BcswPxzOR5RHvvshjdQ7Xb7zfyG1V6KA@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOp6jLZZrmwZ1xZG2AzF+VTzn+zFUFa0EpSXp1T-fSc7ZhNa7A@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOp6jLbbe9PWKfiooQ-jT+0E=zAd9VRqD-XqqCNogvDVmiBxaQ@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOMQ+w9LYiOQ3u=DagEKEMqSeV91RqCMnUgy5zCaZsJw0Fur7g@mail.gmail.com
+Notes:    See also https://drafts.csswg.org/css-overflow-3/#scrollable
+Notes:    See also https://www.w3.org/mid/56415511.5090604@mozilla.com
+Open:     =WG= Review discussions & request changes as necessary.
+Resolved:
    
+
    +Issue 49. #
+Summary:  Apply box-shadow after transform
+From:     Christian Mayer
+Comment:  https://www.w3.org/mid/56C63DB8.8080004@ChristianMayer.de
+Response: https://www.w3.org/mid/CAAWBYDCGcu0S3DFeetReqfb6tV9J0eQay9M3tE=NeKSLTmL8Nw@mail.gmail.com
+Response: https://www.w3.org/mid/CAFDDJ7wQ77_q23i3vJJmGubM6jBiCkbgR3QJcS6VRQk0H0C=kQ@mail.gmail.com
+Response: https://www.w3.org/mid/C095D0EA-9473-4F5C-9E2A-8F7550F31A01@me.com
+Response: https://www.w3.org/mid/56C7D1B2.4030700@inkedblade.net
+Open:     Rejected?
+Resolved: =WG= Discuss.
    
+
    +Issue 50. #
+Summary:  Some cubic-bezier functions output out of range [0,1]
+From:     hiikezoe
+Comment:  https://github.com/w3c/csswg-drafts/issues/744
+Response:
+Open:     =ED= Solve or agenda+.
+Resolved:
    
+
    +Issue 51. #
+Summary:  scale 0 on non-scaling stroke
+From:     Rik Cabanier
+Comment:  http://www.w3.org/mid/CAGN7qDB29wTjx0KVOjpozGckXRevZ-JVkDnFTh1-+1v9FDkEiw@mail.gmail.com
+Comment:  http://www.w3.org/mid/201205121352.41569.Dr.O.Hoffmann@gmx.de
+Response:
+Open:     ?
+Resolved: ?
    
+
    +Issue 52. #
+Summary:  Some comments on the non-scaling stroke spec text
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201205132051.25760.Dr.O.Hoffmann@gmx.de
+Open:     =ED= Edit, file issues, or close as necessary.
+Resolved: Editor discretion
    
+
    +Issue 53. #
+Summary:  skew() is messed up
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201203071410.51426.Dr.O.Hoffmann@gmx.de
+Comment:  http://www.w3.org/mid/C4ADC064-7771-483F-AF81-79D6D54671B4@adobe.com
+Open:     =WG= Discuss.
    
+
    +Issue 54. #
+Summary:  Rendering transforms with non-invertible matrix
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201204221814.06054.Dr.O.Hoffmann@gmx.de
+Open:     =ED= Figure out issue. =WG= Discuss & resolve.
    
+
    +Issue 55. #
+Summary:  animateTransform thread of unclear conclusion
+From:     Dr. Olaf Hoffmann
+Comment:  http://www.w3.org/mid/201204261843.03940.Dr.O.Hoffmann@gmx.de
+Continue: http://www.w3.org/mid/C3DB860D-28F2-4388-9D9E-513597FFAFE4@adobe.com
+Open:     =SVGWG= Figure out if this thread is 100% handled
+Resolved:
    
+
    +Issue 56. #
+Summary:  Deprecate animateTransform
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/86583EBE-30F0-41BD-B3E2-E6D5588BB821@adobe.com
+Open:     =SVGWG= Figure this out and respond to thread.
+Resolved:
    
+
    +Issue 57. #
+Summary:  Neutral element for addition wrt animating transforms
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com
+Open:     =WG= Discuss.
    
+
    +Issue 58. #
+Summary:  Transforms vs background-attachment: fixed
+From:     Simon Fraser
+Comment:  http://www.w3.org/mid/42ED583F-AFF2-4D49-B20A-4335C93EEA23@me.com
+Response: http://www.w3.org/mid/op.wgl87egg4p7avi@localhost.localdomain
+Comment:  http://www.w3.org/mid/CAKA+AxnmG8CynocjdOQR-6WrZDa-uGwGpO74KUMBo0W2x8waWA@mail.gmail.com
+Notes:    https://www.w3.org/Bugs/Public/show_bug.cgi?id=15833
+Response:
+Open:     =WG= Discuss.
    
+
    +Issue 59. #
+Summary:  Use 'will-change' to optimize rasterization
+From:     chrishtr
+Comment:  https://github.com/w3c/csswg-drafts/issues/236
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
    
+
diff --git a/css-transforms/issues-wd-2013.txt b/css-transforms/issues-wd-2013.txt
new file mode 100644
index 00000000000..dcb130df5ae
--- /dev/null
+++ b/css-transforms/issues-wd-2013.txt
@@ -0,0 +1,516 @@
+Draft:    https://www.w3.org/TR/2013/WD-css-transforms-1-20131126/
+Title:    CSS Transforms Level 1
+Dates:    2012/05/01 through 2016/12/29
+
+2D Transforms Only (3D Transforms move to L2 per WG resolution)
+
+Unfiled threads:
+  * Someone figure out if thread at https://www.w3.org/mid/F1CB6513-BAD8-4CCA-8658-194EDEB7C2C8@andrewdupont.net concluded?
+  * Ditto http://www.w3.org/mid/510806D8.5050403@w3.org
+  * Make sure https://www.w3.org/mid/B7126E1C-EB7C-4D9F-9238-F9CDD72BDB21@adobe.com doesn't affect 2D else file it herein.
+  * Is http://www.w3.org/mid/CAGN7qDBomdt1QFyM_VsydiY=Vo-PcyX9T7ZSHb8raEA=-Vfvjg@mail.gmail.com filed somewhere?
+
+Issues are thematically sorted.
+Recommend to start with will-change issue, then start at the top and work down.
+
+----
+Issue 1.
+Summary:  Issues list link is outdated
+From:     Rick Byers
+Comment:  https://github.com/w3c/csswg-drafts/issues/486
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial
+----
+Issue 2.
+Summary:  Add more info to “Module Interactions”
+From:     Dirk Schulze
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=17237
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial
+----
+Issue 3.
+Summary:  Convert to <*-percentage> notation
+From:     Sebastian Zartner (SebastianZ)
+Comment:  https://github.com/w3c/csswg-drafts/issues/645
+Response:
+Open:     =ED= Edit.
+Resolved: Editorial.
+----
+Issue 4.
+Summary:  Define transform list using grammar
+From:     Sebastian Zartner
+Comment:  https://www.w3.org/mid/CAERejNZgyWKV5ioh3KR9BmYYrvpM5919D9z1Qb-LjQ5zBGOFuQ@mail.gmail.com
+Response: http://www.w3.org/mid/CAAWBYDCB7nP+rqj7DzAef6zqMHtvoshLGMJuL7PsMi-V9qvPfw@mail.gmail.com
+Closed:   Invalid
+----
+Issue 5.
+Summary:  Clarify matrix index convention
+From:     Maurizio Casimirri
+Comment:  http://www.w3.org/mid/C73D086A-A220-48E3-A3DC-6195D350C3FA@gmail.com
+Open:     =ED= Edit.
+Resolved: Editorial
+----
+Issue 6.
+Summary:  Confusion about multiplication
+From:     Simon Sapin & Boris Zbarsky
+Comment:  https://www.w3.org/mid/509FCC62.5080101@mit.edu
+Response:
+Open:     =ED= Make sure comments in thread are all addressed
+Resolved: Bugfix
+----
+Issue 7.
+Summary:  Application of transform to inlines
+From:     Gérard Talbot
+Comment:  https://www.w3.org/mid/b464220dd959f9a9f808dd4aad85288e@gtalbot.org
+Comment:  http://www.w3.org/mid/20140210195906.GA18205@crum.dbaron.org
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 8.
+Summary:  Computed Style of 'transform'
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/A020C5AD-51B0-4288-8D8A-9D8322213D5B@adobe.com
+Comment:  http://www.w3.org/mid/20140325212945.GA26872@crum.dbaron.org
+Response: http://www.w3.org/mid/314879EA-CF63-4792-90DD-36000224B04F@adobe.com
+Open:     =ED= Verify if fixed, else edit.
+Resolved: Bugfix
+Verified: [need a response where dbaron says it's all good now]
+----
+Issue 9.
+Summary:  Error in order of multiple transform function
+From:     rosenau
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29110
+Response:
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 10.
+Summary:  Clarify behavior for gradientTransform and patternTransform
+From:     Erik Dahlström
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=26470
+Response:
+Open:     =Dirk= Deal. or =WG= Discuss.
+----
+Issue 11.
+Summary:  Use of “containing block” does not match CSS2.1 definition
+From:     Aryeh Gregor
+From:     Simon Sapin
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=16328
+Comment:  http://www.w3.org/mid/514E058C.5060105@exyr.org
+Response:
+Notes:    See also dbaron's message in the issue below.
+Open:     =ED= Figure out what to do.
+Resolved: Editor discretion (or agenda+ if there's a problem)
+----
+Issue 12.
+Summary:  Spec doesn't mention establishing abspos containing block
+From:     Robert O'Callahan
+Comment:  https://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com
+From:     David Baron
+Comment:  https://www.w3.org/mid/20151125002414.GA22745@pescadero.dbaron.org
+Response:
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 13.
+Summary:  Interaction of regions and transforms and abspos/fixedpos
+From:     Mihnea-Vlad Ovidenie
+Comment:  https://www.w3.org/mid/CE4E28E9.4B01C%25mihnea@adobe.com
+Response: =astearns= File against Regions
+Closed:   Out-of-Scope
+----
+Issue 14.
+Summeray: Specify stack level of non-positioned transformed elements
+From:     Øyvind Stenhaug
+Comment:  http://www.w3.org/mid/op.wg8psjr1bunlto@oyvinds-desktop
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 15.
+Summary:  Clarify Appendix E rendering of 2D transformed descendants
+From:     David Baron
+Comment:  http://www.w3.org/mid/20150904234527.GA15137@pescadero.dbaron.org
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Bugfix
+----
+Issue 16.
+Summary:  transform functions should accept percentages
+From:     Boris Zbarsky
+Comment:  https://www.w3.org/mid/546F5D45.6030704@mit.edu
+Response: https://www.w3.org/mid/A2D81F68-B51F-468C-8C10-50D435980254@adobe.com
+Closed:   Accepted
+Resolved: Bugfix
+----
+Issue 17.
+Summary:  Define basis for percentage transform on patterns, gradients, clipPath
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/9B0DDCB4-B480-471F-943A-C5ED00598DFA@adobe.com
+Changes:
+Open:     =WG= Discuss.
+----
+Issue 18.
+Summary:  Match SVG spec for interaction with object bounding box units
+From:     Amelia Bellamy-Royds
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28385
+Response:
+Changes:
+Open:     =ED= Edit.
+Resolved: Editor discretion.
+----
+Issue 19.
+Summary:  Update “transformable elements” for SVG2
+From:     Nikos Andronikos
+Comment:  https://github.com/w3c/csswg-drafts/issues/358
+Response:
+Changes:
+Open:     =ED= Edit
+Resolved: Editor discretion
+----
+Issue 20.
+Summary:  Units aren't back-compatible with old SVG
+From:     Dr. Olaf Hoffman
+Comment:  https://www.w3.org/mid/201204211629.13408.Dr.O.Hoffmann@gmx.de
+Response: https://www.w3.org/mid/3DCACD7B-0115-44FC-901A-A86DC1211CD1@adobe.com
+Closed:   Rejected
+Resolved: Editor discretion
+----
+Issue 21.
+Summary:  Unitless values
+From:     Tab Atkins
+Comment:  http://www.w3.org/mid/CAAWBYDDDDMY0czypkLQ2X8tBtLFjYn5t9g+aYOPBzXLEAGzBzA@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAAWBYDD3VfCvDfe0TEUJEd7e+JXZzhRDGTyEgdc9Hodz0pCLUQ@mail.gmail.com
+Open:     =ED= Edit.
+Resolved: =WG= Resolve.
+----
+Issue 22.
+Summary:  Transform syntax CSS vs SVG harmonization
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/7E680372-9199-4AF9-98A1-C7B6ECB72C87@adobe.com
+Response: https://www.w3.org/mid/88568E75-27C9-4DA4-BCD6-7459FA5D9FE4@adobe.com
+Open:     Accepted
+Resolved: =WG= Review.
+----
+Issue 23.
+Summary:  User coordinate space statement breaks SVG
+From:     Amelia Bellamy-Royds
+Comment:  http://www.w3.org/mid/CAFDDJ7yhF7Qn28wVMqb7ra6N9Q=j74OTqHWpjLeYrH=LQwmd4A@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
+----
+Issue 24.
+Summary:  Issues with transform on SVG root
+From:     Dirk Schulze
+Comment:  https://www.w3.org/mid/0A9D2705-9FFE-425B-B3CB-297EA97D337D@adobe.com
+Open:     =SVGWG= Figure out if anything remains to be done.
+----
+Issue 25.
+Summary:  Transforms on root SVG element
+From:     Amelia Bellamy-Royds
+Comment:  http://www.w3.org/mid/CAFDDJ7xQp+j2c+18zkRyPWPtnuk+dbVA6Dc_L7ACr-tptAGicA@mail.gmail.com
+Response:
+Open:     =WG= Discuss with SVG folks
+----
+Issue 26.
+Summary:  Use UA style sheet instead of prose for SVG transform-origin
+From:     Dirk Schulze
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28000
+Comment:  https://www.w3.org/mid/20150611085235.GA3929@wok.mcc.id.au
+Response: https://www.w3.org/mid/CE3AFDB0-D260-493A-9110-16BB01D8E28E@adobe.com
+Open:     =ED= Edit.
+Resolved: Editor discretion
+----
+Issue 27.
+Summary:  Specs disagree on whether transform-origin's resolved value is used or computed
+From:     Xidorn Quan
+Comment:  https://github.com/w3c/csswg-drafts/issues/392#issuecomment-238494067
+Proposal: https://github.com/w3c/csswg-drafts/issues/392#issuecomment-269639534
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 28.
+Summary:  transform-origin relative to containing block
+From:     Xidorn Quan
+Comment:  https://www.w3.org/mid/CAMdq698_DMux4CFD6pA2MOdK7VX9yCWJgciXE0_MuRxXAV1WMA@mail.gmail.com
+Response: https://www.w3.org/mid/CAMdq698unKqMTgJpVXFmRtcmcjfwEkhGfmhhk0dsZgxiQ4E6uQ@mail.gmail.com
+Closed:   Retracted
+----
+Issue 29.
+Summary:  Add transform-origin-x/y?
+From:     Boris Zbarsky
+Comment:  https://www.w3.org/mid/50648288.4050309@mit.edu
+Response:
+Note:     CSS Backgrounds L4 solved the logical coords problem
+          since this thread was last discussed.
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 30.
+Summary:  transform-origin: 0% not equivalent to 0px is confusing
+From:     Cameron McCormack
+Comment:  https://www.w3.org/mid/525F2287.8050002@mcc.id.au
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 31.
+Summary:  exact definition of origin argument to rotate()
+From:     Rik Cabanier
+Comment:  http://www.w3.org/mid/CAGN7qDC=oAU5XQt0E7sJ=2vcMLU1BzmH4L7EzYsfvtL-5LbHZQ@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAKA+Axk=-C3tTdoKRU3g2Be=GV3aeiNfqYot3205h6fZVP2K=w@mail.gmail.com
+Comment:  http://www.w3.org/mid/CAGN7qDD9LftfaCqnH_oPXe78GqYv2aOdE8forTWN515=-UHRmg@mail.gmail.com
+Proposal: http://www.w3.org/mid/CAGN7qDAw3eU72K-QSeMVmqPjh0_wihnBf7rG4bsVsQnfVSDJ5g@mail.gmail.com
+Changes:  [link to relevant section(s)]
+Open:     =ED= Needs edits?
+Resolved: =WG= Discuss.
+----
+Issue 32.
+Summary:  Unitless zero rotation
+From:     Simon Fraser
+Comment:  https://www.w3.org/Bugs/Public/show_bug.cgi?id=29413
+Response:
+Open:     =ED= Update to reference CSS Values 3 correctly?
+Resolved: [Sydney F2F 2016? need to find minutes]
+----
+Issue 33.
+Summary:  Make Rotation Less Weird
+From:     Shane Stephens
+Comment:  https://www.w3.org/mid/CAGTfzwT8M0_c1Wnk5To1zRVtGXtuLzXbjkpDS55DC6T9dUTfKQ@mail.gmail.com
+Notes:    See also zero-coord axis issue below.
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 34.
+Summary:  Reduce matrix decomposition when rotation axis has zero coord
+From:     Shane Stephens
+Comment:  http://www.w3.org/mid/CAGTfzwTS9r+z1LRu=3t25NW0A6yk0b+agaH6__8ZkcSD3-LR9A@mail.gmail.com
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 35.
+Summary:  Interpolation of transform lists
+From:     David Baron
+Comment:  http://www.w3.org/mid/20120719213826.GA8775@crum.dbaron.org
+Response: http://www.w3.org/mid/474B73CD-95F5-467B-9F39-90D7045E3A9C@adobe.com
+Closed:   Accepted
+Resolved: ?
+Verified: [get verification from dbaron]
+----
+Issue 36.
+Summary:  Add null transform as placeholder for animations?
+From:     CSSWG
+Comment:  http://www.w3.org/mid/523AB5BE.50406@inkedblade.net
+Response:
+Open:     =WG= Discuss or defer.
+Resolved:
+----
+Issue .37
+Summary:  Smarter interpolation of truncated transform lists
+From:     Louis-Rémi Babé
+Comment:  https://www.w3.org/mid/CALXxKfCKZd+P0mH2oFyDkBgps56WqwQnLSMpKk1nrqiFXScqVA@mail.gmail.com
+Response: https://www.w3.org/mid/CAAWBYDBPafEbiXNy=Mw4a9w1jmvK6dUJzq28PPjN7APgtjqAEw@mail.gmail.com
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 38.
+Summary:  Transform interpolation problem
+From:     David Baron
+Comment:  https://www.w3.org/mid/20140702002134.GA26687@crum.dbaron.org
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 39.
+Summary:  Interpolated values don't interpolate well with original start/end
+From:     David Baron
+Comment:  https://www.w3.org/mid/20140226234818.GA5390@crum.dbaron.org
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 40.
+Summary:  Bugs in interpolation algorithm
+From:     Manish Goregaokar (Manishearth)
+Comment:  https://github.com/w3c/csswg-drafts/issues/483#issuecomment-249497761
+Response:
+Changes:
+Open:     =ED= Edit or ask for help.
+Resolved: Bugfix.
+----
+Issue 41.
+Summary:  Matrix Interpolation
+From:     Shane Stephens
+Comment:  http://www.w3.org/mid/CADhPm3tF-tBQMwhOWRAYN-L+rVPhX-_xAa6ynKGa57Ue4HMywA@mail.gmail.com
+Notes:    Might be further background elsewhere, didn't find it. But see below.
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 42.
+Summary:  Use better matrix interpolation method
+From:     Ken Shoemake
+From:     Benoit Jacob
+Comment:  http://www.w3.org/mid/52CD882F.6020408@yahoo.com
+Comment:  http://www.w3.org/mid/CAJTmd9qXg+WAt5OK9g-pTEwHunEXxcKtvBSJ4fd_5=SmLHM-jg@mail.gmail.com
+Response:
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 43.
+Summary:  Matrix Decomposition
+From:     Dirk Schulze
+From:     Rik Cabanier
+Comment:  https://www.w3.org/mid/A54A72B2-5BFB-46F7-8B08-BE2B7A3EA8D2@adobe.com
+Comment:  http://www.w3.org/mid/CAGN7qDBdtR1AWowudWzrj0ownknbvatv-HhC1E28_QJYSB47aQ@mail.gmail.com
+Open:     =WG= Discuss.
+Resolved:
+----
+Issue 44.
+Summary:  Include Tagaki-san's definition of linear scale
+From:     CSSWG
+Comment:  http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com
+Open:     =ED= Edit.
+Resolved: http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com
+----
+Issue 45.
+Summary:  getTransformToElement needs more detail
+From:     CSSWG
+Comment:  https://www.w3.org/mid/CADhPm3t+PxH+eCXcOxiX61J_Nx+jimkttsoViSCQNDSVOTKNDQ@mail.gmail.com
+Response:
+Changes:
+Open:     Needs proposed text.
+Resolved:
+----
+Issue 46.
+Summary:  transform-box values & correspondance to SVG vs CSS
+From:     Erik Dahlström
+Comment:  https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain
+Response:
+Notes:    See also https://drafts.fxtf.org/paint/#fill-origin
+Open:     =WG= Discuss, and ensure alignment with FXTF Paint.
+Resolved:
+Notes:    This should have an all-WG resolution since it crosses multiple modules
+----
+Issue 47.
+Summary:  Scrollbars vs. scaling down
+From:     Tab Atkins
+Comment:  https://www.w3.org/mid/CAAWBYDDX2ECLHm523xNpr8qqYgsqeU2SXiY0GvZo7S1063CoAg@mail.gmail.com
+Response: https://www.w3.org/mid/CAOp6jLYZ8VMPW4wNOMkH_uLPROr1ows22AFgLqMuhzQ=h89m0A@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAAWBYDDfy0ghxEB5jnSTP3LMTbGo1=p=Wq5GUizw3RySS6QGJA@mail.gmail.com
+Response: https://www.w3.org/mid/CAOp6jLYTvsqEYfUv=mfayYADuJnZKhC1vakfdqsFvrPu0Tp_7A@mail.gmail.com
+Closed:   Invalid
+Verified: =ED= Verify.
+----
+Issue 48.
+Summary:  Impact of transforms on scrollable area (multiple threads)
+From:     Robert O'Callahan
+Comment:  http://www.w3.org/mid/CAOp6jLbN9SjQd4zRy=BcswPxzOR5RHvvshjdQ7Xb7zfyG1V6KA@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOp6jLZZrmwZ1xZG2AzF+VTzn+zFUFa0EpSXp1T-fSc7ZhNa7A@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOp6jLbbe9PWKfiooQ-jT+0E=zAd9VRqD-XqqCNogvDVmiBxaQ@mail.gmail.com
+Comment:  https://www.w3.org/mid/CAOMQ+w9LYiOQ3u=DagEKEMqSeV91RqCMnUgy5zCaZsJw0Fur7g@mail.gmail.com
+Notes:    See also https://drafts.csswg.org/css-overflow-3/#scrollable
+Notes:    See also https://www.w3.org/mid/56415511.5090604@mozilla.com
+Open:     =WG= Review discussions & request changes as necessary.
+Resolved:
+----
+Issue 49.
+Summary:  Apply box-shadow after transform
+From:     Christian Mayer
+Comment:  https://www.w3.org/mid/56C63DB8.8080004@ChristianMayer.de
+Response: https://www.w3.org/mid/CAAWBYDCGcu0S3DFeetReqfb6tV9J0eQay9M3tE=NeKSLTmL8Nw@mail.gmail.com
+Response: https://www.w3.org/mid/CAFDDJ7wQ77_q23i3vJJmGubM6jBiCkbgR3QJcS6VRQk0H0C=kQ@mail.gmail.com
+Response: https://www.w3.org/mid/C095D0EA-9473-4F5C-9E2A-8F7550F31A01@me.com
+Response: https://www.w3.org/mid/56C7D1B2.4030700@inkedblade.net
+Open:     Rejected?
+Resolved: =WG= Discuss.
+----
+Issue 50.
+Summary:  Some cubic-bezier functions output out of range [0,1]
+From:     hiikezoe
+Comment:  https://github.com/w3c/csswg-drafts/issues/744
+Response:
+Open:     =ED= Solve or agenda+.
+Resolved:
+----
+Issue 51.
+Summary:  scale 0 on non-scaling stroke
+From:     Rik Cabanier
+Comment:  http://www.w3.org/mid/CAGN7qDB29wTjx0KVOjpozGckXRevZ-JVkDnFTh1-+1v9FDkEiw@mail.gmail.com
+Comment:  http://www.w3.org/mid/201205121352.41569.Dr.O.Hoffmann@gmx.de
+Response:
+Open:     ?
+Resolved: ?
+----
+Issue 52.
+Summary:  Some comments on the non-scaling stroke spec text
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201205132051.25760.Dr.O.Hoffmann@gmx.de
+Open:     =ED= Edit, file issues, or close as necessary.
+Resolved: Editor discretion
+----
+Issue 53.
+Summary:  skew() is messed up
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201203071410.51426.Dr.O.Hoffmann@gmx.de
+Comment:  http://www.w3.org/mid/C4ADC064-7771-483F-AF81-79D6D54671B4@adobe.com
+Open:     =WG= Discuss.
+----
+Issue 54.
+Summary:  Rendering transforms with non-invertible matrix
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/201204221814.06054.Dr.O.Hoffmann@gmx.de
+Open:     =ED= Figure out issue. =WG= Discuss & resolve.
+----
+Issue 55.
+Summary:  animateTransform thread of unclear conclusion
+From:     Dr. Olaf Hoffmann
+Comment:  http://www.w3.org/mid/201204261843.03940.Dr.O.Hoffmann@gmx.de
+Continue: http://www.w3.org/mid/C3DB860D-28F2-4388-9D9E-513597FFAFE4@adobe.com
+Open:     =SVGWG= Figure out if this thread is 100% handled
+Resolved:
+----
+Issue 56.
+Summary:  Deprecate animateTransform
+From:     Dr. Olaf Hoffman
+Comment:  http://www.w3.org/mid/86583EBE-30F0-41BD-B3E2-E6D5588BB821@adobe.com
+Open:     =SVGWG= Figure this out and respond to thread.
+Resolved:
+----
+Issue 57.
+Summary:  Neutral element for addition wrt animating transforms
+From:     Dirk Schulze
+Comment:  http://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com
+Open:     =WG= Discuss.
+----
+Issue 58.
+Summary:  Transforms vs background-attachment: fixed
+From:     Simon Fraser
+Comment:  http://www.w3.org/mid/42ED583F-AFF2-4D49-B20A-4335C93EEA23@me.com
+Response: http://www.w3.org/mid/op.wgl87egg4p7avi@localhost.localdomain
+Comment:  http://www.w3.org/mid/CAKA+AxnmG8CynocjdOQR-6WrZDa-uGwGpO74KUMBo0W2x8waWA@mail.gmail.com
+Notes:    https://www.w3.org/Bugs/Public/show_bug.cgi?id=15833
+Response:
+Open:     =WG= Discuss.
+----
+Issue 59.
+Summary:  Use 'will-change' to optimize rasterization
+From:     chrishtr
+Comment:  https://github.com/w3c/csswg-drafts/issues/236
+Response:
+Changes:
+Open:     =WG= Discuss.
+Resolved:
+----
diff --git a/css-transitions/Overview.bs b/css-transitions/Overview.bs
index f21eba80b77..aeb5fcda4f7 100644
--- a/css-transitions/Overview.bs
+++ b/css-transitions/Overview.bs
@@ -46,7 +46,7 @@ Ignored Vars: x1, x2, y1, y2
 Link Defaults: css-transforms (property) transform
 
    -spec:css21; type:property;
+spec:css2; type:property;
     text:top
     text:right
     text:bottom
@@ -88,6 +88,9 @@ spec:css21; type:property;
     text:visibility
     text:word-spacing
     text:z-index
+spec:css-backgrounds-3; type:property;
+    text:background-image
+    text:background-origin
 spec:css-color-3;
     type:property;
         text:color
diff --git a/css-values/Overview.bs b/css-values/Overview.bs
index e89ea5eea8c..92320554623 100644
--- a/css-values/Overview.bs
+++ b/css-values/Overview.bs
@@ -52,7 +52,7 @@ Module Interactions
 	4.3,
 	and A.2.
 
-
 
-
 
 
    
-Font-relative lengths: the ''em'', ''ex'', ''ch'', ''ic'', ''rem'' units
    
+Font-relative lengths: the 
+''em'', 
+''rem'', 
+''ex'', 
+''cap'',
+''ch'', 
+''ic'' 
+units
 
 	Aside from ''rem'' (which refers to the font-size of the root element),
 	the font-relative lengths refer to the font metrics of the element on which they are used.
@@ -942,20 +953,38 @@ Font-relative lengths: the ''em'', ''ex'', ''ch'', ''ic'', ''rem'' units
 				will be 20% greater than the computed font size inherited by h1 elements.
 			
 
+		
    rem unit
+		
    
+			Equal to the computed value of 'font-size' on the root element.
+			When specified on the 'font-size' property of the root element,
+			the ''rem'' units refer to the property's initial value.
+
 		
    ex unit
 		
    
 			Equal to the used x-height of the first available font [[!CSS3-FONTS]].
-			The x-height is so called because it is often equal to the height of the lowercase "x".
+			The x-height is so called because it is often equal to the height of the lowercase "x" (U+0078).
 			However, an ''ex'' is defined even for fonts that do not contain an "x".
-			The x-height of a font can be found in different ways. Some fonts
-			contain reliable metrics for the x-height. If reliable font metrics
-			are not available, UAs may determine the x-height from the height
-			of a lowercase glyph. One possible heuristic is to look at how far
-			the glyph for the lowercase "o" extends below the baseline, and
-			subtract that value from the top of its bounding box. In the cases
-			where it is impossible or impractical to determine the x-height,
+			
+			The x-height of a font can be found in different ways. 
+			Some fonts contain reliable metrics for the x-height. 
+			If reliable font metrics are not available, 
+			UAs may determine the x-height from the height of a lowercase glyph. 
+			One possible heuristic is to look at 
+			how far the glyph for the lowercase "o" extends below the baseline, and
+			subtract that value from the top of its bounding box. 
+			
+			In the cases where it is impossible or impractical to determine the x-height,
 			a value of 0.5em must be assumed.
 
+		
    cap unit
+		
    
+			Equal to the used H-height of the first available font.
+			The H-height is so called because it is often equal to the height of the uppercase "H" (U+0048).
+			However, a ''cap'' is defined even for fonts that do not contain an "H".
+
+			In the cases where it is impossible or impractical to determine the H-height,
+			a value of 1em must be assumed.
+
 		
    ch unit
 		
    
 			Equal to the used advance measure of the “0” (ZERO, U+0030) glyph
@@ -978,12 +1007,20 @@ Font-relative lengths: the ''em'', ''ex'', ''ch'', ''ic'', ''rem'' units
 			(i.e. 'writing-mode' is ''vertical-rl'' or ''vertical-lr''
 			and 'text-orientation' is ''text-orientation/upright'').
 
-		
    ic unit
+		
    en unit
+		
    
+			Equal to the used advance measure of the “–” (EN DASH, U+2013) glyph
+			in the font used to render it.
+
+			In the cases where it is impossible or impractical to determine the measure of the “–” glyph,
+			a value of 0.5em must be assumed.
+
+		
    ic unit
 		
    
 			Equal to the used advance measure of the “水” (CJK water ideograph, U+6C34) glyph
 			found in the font used to render it.
 
-			This measurement is a typically an exact measure
+			This measurement is typically an exact measure
 			(in the few fonts with proportional fullwidth glyphs, an approximation)
 			of a single fullwidth glyph’s advance measure,
 			thus allowing measurements based on an expected glyph count.
@@ -991,14 +1028,41 @@ Font-relative lengths: the ''em'', ''ex'', ''ch'', ''ic'', ''rem'' units
 			In the cases where it is impossible or impractical to determine the ideographic advance measure,
 			it must be assumed to be 1em.
 
-		
    rem unit
+		
    bs unit
 		
    
-			Equal to the computed value of 'font-size' on the root element.
-			When specified on the 'font-size' property of the root element,
-			the ''rem'' units refer to the property's initial value.
+			Equal to the used base stroke thickness of the first available font.
+			The base stroke thickness is the width of primary stems, 
+			usually straight vertical strokes.
+			
+			The stroke widths of a font can be found in different ways. 
+			Some fonts contain reliable metrics for the stroke widths. 
+			If reliable font metrics are not available, 
+			UAs may determine the base stroke width from 
+			the median width of a vertical stem in a lowercase glyph with ascender, 
+			e.g. "h".
+			
+			In the cases where it is impossible or impractical to determine the base stroke thickness, 
+			a value of 0.0625em must be assumed. 
+			This is 1px for the common default font size of 16px.
+
+		
    hs unit
+		
    
+			Equal to the used hair-line stroke thickness of the first available font.
+			The hair-line stroke thickness is the width of secondary vertical stems, 
+			often straight horizontal or diagonal strokes. 
+			In some fonts, by design, it does not differ from the base stroke thickness.
+			
+			If reliable font metrics are not available, 
+			UAs may determine the hair-line stroke width from 
+			the median width of a horizontal bar in a lowercase glyph, 
+			e.g. "e".
+			
+			In the cases where it is impossible or impractical to determine the hair-line stroke thickness, 
+			a value of 1bs must be assumed.
+
 	
 
-
 
 
    
-Viewport-percentage lengths: the ''vw'', ''vh'', ''vi'', ''vb'', ''vmin'', ''vmax'' units
    
+Viewport-percentage lengths: the 
+''vw'', ''vh'', 
+''vi'', ''vb'', 
+''vmin'', ''vmax'' 
+units
 
 	The viewport-percentage lengths are relative to the size of the
 	initial containing block.
@@ -1038,15 +1106,17 @@ Viewport-percentage lengths: the ''vw'', ''vh'', ''vi'', ''vb'', ''vmin'', ''vma
 		
    vh unit
 		
    
 			Equal to 1% of the height of the initial containing block.
-		
    vi unit
+
+		
    vi unit
 		
    
 			Equal to 1% of the size of the initial containing block
-			in the direction of the root element's inline axis.
+			in the direction of the root element's inline axis.
 
-		
    vb unit
+		
    vb unit
 		
    
 			Equal to 1% of the size of the initial containing block
-			in the direction of the root element's block axis.
+			in the direction of the root element's block axis.
+
 		
    vmin unit
 		
    
 			Equal to the smaller of ''vw'' or ''vh''.
@@ -1062,7 +1132,7 @@ Viewport-percentage lengths: the ''vw'', ''vh'', ''vi'', ''vb'', ''vmin'', ''vma
 	the ''vi'' and ''vb'' units use the initial value of the 'writing-mode' property
 	to determine which axis they correspond to.
 
-
 
 
    
-Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' units
    
+Absolute lengths: the 
+''m'', ''dm'', 
+''cm'', ''mm'', 
+''mu'', 
+''mdl'', ''thm'', 
+''cc'', ''dd'', 
+''q''; 
+''yd'', ''ft'', 
+''in'', ''pc'', ''pt'', 
+''sx'', ''tx'', ''twip'', 
+''ax'', ''ay'', ''bx'', ''by'', ''cx'', ''cy'', 
+''dot'', 
+and ''px'' 
+units
 
 	The absolute length units are fixed in relation to each other
 	and anchored to some physical measurement.
 	They are mainly useful when the output environment is known.
 	The absolute units consist of
-	the physical units (''in'', ''cm'', ''mm'', ''pt'', ''pc'', ''q'')
+	the physical units (''m'', 
+	''yd'', ''ft'', 
+	''hd'', 
+	''dm'', 
+	''ax'', ''ay'', ''bx'', ''by'', ''cx'', ''cy'', 
+	''in'', ''cm'', 
+	''cc'', 
+	''pc'', ''mm'', 
+	''sx'', ''tx''
+	''dd'', 
+	''pt'', 
+	''q'', 
+	''twip'', 
+	''dot'', 
+	''um'')
 	and the visual angle unit (''px''):
 
 	
@@ -1088,27 +1185,93 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit
 		    
+		
    name
 		    equivalence
 	
    m
+		    meters
+		    1m = 1000mm
+		
    dm
+		    decimeters
+		    1dm = 100mm
 		
    cm
 		    centimeters
-		    1cm = 96px/2.54
+		    1cm = 10mm
 		
    mm
 		    millimeters
-		    1mm = 1/10th of 1cm
+		    1mm = 96px/25.4 
+		
    mu
+			
+		    micrometers (μm), "microns"
+		    1mu = 1mm/1000
 		
    Q
-		    quarter-millimeters
-		    1q = 1/40th of 1cm
+		    quarter-millimeters (キゥ)
+		    1q = 1mm/4
+		
    cc
+		    ciceros
+		    1cc = 12dd = 18q
+		
    dd
+		    didots
+		    1dd = 3mm/8 = 1.5q
+		
    thm
+			
+		    thumbs
+		    1thm = 25mm
+		
    mdl
+			
+		    modules
+		    1mdl = 300mm = 12thm
+		
    dot
+		    dots 
+		    	
+		    1dot = 1mm/1440
 		
    in
 		    inches
-		    1in = 2.54cm = 96px
+		    1in = 25.4mm = 96px
 		
    pc
 		    picas
-		    1pc = 1/6th of 1in
+		    1pc = 1in/6 = 12pt = 16px
+		
    sx
+			
+		    sixteenth-inches
+		    1sx = 1in/16 = 6px
+		
    tx
+		    thirtysecondth-inches
+		    1tx = 1in/32 = 3px
 		
    pt
 		    points
-		    1pt = 1/72th of 1in
+		    1pt = 1in/72
 		
    px
 		    pixels
-		    1px = 1/96th of 1in
+		    1px = 1in/96
+		
    twip
+		    twentieth-points
+		    1twip = 1in/1440 = 1pt/20
+		
    hd
+		    hands
+		    1hd = 4in
+		
    ft
+		    feet
+		    1ft = 12in = 3hd
+		
    yd
+		    yards
+		    1yd = 36in = 3ft
+		
    ay
+		    long side of A10 paper
+		    1ay = 2-4.75m ≈ 37.163mm
+		
    ax
+		    short side of A10 paper
+		    1ax = 2-5.25m ≈ 26.278mm
+		    
+		
    by
+		    long side of B10 paper
+		    1by = 2-4.5m ≈ 44.194mm
+		
    bx
+		    short side of B10 paper
+		    1bx = 2-5m = 31.25mm
+		
    cy
+		    long side of C10 paper
+		    1cy = 2-4.625m ≈ 40.526mm
+		
    cx
+		    short side of C10 paper
+		    1cx = 2-5.125m ≈ 28.656mm
 	
    
 
 	
    
@@ -1117,12 +1280,18 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit
 		h2 { line-height: 3cm }   /* centimeters */
 		h3 { word-spacing: 4mm }  /* millimeters */
 		h3 { letter-spacing: 1Q } /* quarter-millimeters */
-		h4 { font-size: 12pt }    /* points */
+ 		h4 { font-size: 14pt }    /* points */
 		h4 { font-size: 1pc }     /* picas */
 		p  { font-size: 12px }    /* px */
    +
    + Abbreviations ''pt'' and ''dd'' also exist in Teχ, + but refer to slightly different definitions. + The equivalent units there are ‘bp’ and ‘nd’, respectively. +
    + All of the absolute length units are compatible, and ''px'' is their canonical unit. @@ -1157,8 +1326,8 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit The reference pixel is the visual angle of one pixel on a device with a pixel density of 96dpi and a distance from the reader of an arm's length. - For a nominal arm's length of 28 inches, - the visual angle is therefore about 0.0213 degrees. + For a nominal arm's length, + the visual angle is about 0.0213 degrees. For reading at arm's length, 1px thus corresponds to about 0.26 mm (1/96 inch). @@ -1173,13 +1342,13 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit alt="This diagram illustrates how the definition of a pixel depends on the users distance from the viewing surface (paper or screen). - The image depicts the user looking at two planes, one - 28 inches (71 cm) from the user, the second 140 inches - (3.5 m) from the user. An expanding cone is projected - from the user's eye onto each plane. Where the cone - strikes the first plane, the projected pixel is 0.26 mm - high. Where the cone strikes the second plane, the - projected pixel is 1.4 mm high."> + The image depicts the user looking at two planes, + one 71 cm from the user, the second 3.5 m from the user. + An expanding cone is projected from the user's eye onto each plane. + Where the cone strikes the first plane, + the projected pixel is 0.26 mm high. + Where the cone strikes the second plane, + the projected pixel is 1.3 mm high.">
    Showing that pixels must become larger if the viewing distance increases
    @@ -1196,7 +1365,7 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit The image depicts a high resolution (large dot density) laser printer output on the left and a low resolution monitor screen on the right. For the laser printer, one - square reference pixel is implemented by 16 dots. For + square reference pixel is implemented by up to 16 dots. For the monitor screen, one square reference pixel is implemented by a single dot.'>
    Showing that more device pixels (dots) are needed to cover a 1px by 1px area @@ -1204,10 +1373,77 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit (of the same approximate viewing distance)
    + + +

    +Anthropometric lengths: the +''tip'', ''tap'', +''mark'', ''pad'', ''span'', +and ''sole'' +units

    + + The anthropometric length units + relate to measurements of a typical human body. + They are mainly useful when output and input device are the same, + e.g. for the dimensions of tap targets on touchscreens. + Unlike absolute units, the anthropometric units are not affected + by viewing distance or device resolution. + UAs may adapt values based upon acquired knowledge + about the system, i.e. device dimensions and user measurements. + The default values are specified in SI centimetres, not CSS ''cm''. + +
    +
    tip unit +
    + The diameter of a circle enclosing a tap with + the tip of a human index finger. + Defaults to 0.5 cm. + +
    tap unit +
    + The diameter of a circle enclosing a tap with + the full print of a human index finger. + Defaults to 1 cm. + +
    mark unit + +
    + The diameter of a circle enclosing a print mark left by + a human thumb. + Defaults to 2.5 cm. + +
    pad unit + +
    + The diameter of a circle enclosing a touch with + the palm of a open human hand excluding fingers. + Defaults to 10 cm. + +
    span unit +
    + The diameter of a circle enclosing a touch with + a open human hand including splayed fingers. + Defaults to 20 cm. + +
    sole unit + +
    + The diameter of a circle enclosing the print + of a single human foot (with shoe). + Defaults to 30 cm. +

    Other Quantities

    -

    -Angle Units: the <> type and ''deg'', ''grad'', ''rad'', ''turn'' units

    +Angle Units: the <> type and +''deg'', +''moa'', ''soa'', +''grad'', ''rad'', +''pi'', +''turn'', +''perm'' +units Angle values are <>s denoted by <angle>. However, for zero angles the unit identifier is optional @@ -1226,29 +1469,61 @@ Angle Units: the <> type and ''deg'', ''grad'', ''rad'', ''turn'' units"> -
    deg +
    deg unit
    Degrees. There are 360 degrees in a full circle. -
    grad +
    moa unit + +
    + Minutes of arc "′". + There are 21,600 minutes in a full circle, 60 in a degree. + +
    soa unit + +
    + Seconds of arc "″". + There are 1,296,000 seconds in a full circle, 60 in a minute. + +
    grad unit
    Gradians, also known as "gons" or "grades". There are 400 gradians in a full circle. -
    rad +
    rad unit +
    + Radians. + There are 2π radians in a full circle. + +
    pi unit + +
    + π-radians. + There are 2 π-radians in a full circle. + +
    turn unit +
    - Radians. There are 2π radians in a full circle. + Turns, also known as "τ-radians". + There is 1 turn in a full circle. -
    turn +
    perm unit
    - Turns. There is 1 turn in a full circle. + Permille "‰", also known as "parts per thousand", + and mostly used for gradients, + is defined as the ratio of elevation by ground distance. + That means, a 1 mm rise over 100 mm has a slope of 10‰ (or 1%). +
    For example, a right angle is ''90deg'' or ''100grad'' or ''0.25turn'' or - approximately ''1.57rad''. + ''0.5pi'' or approximately ''1.57rad'', + but undefined (positive infinity) for ''perm''. - All <> units are compatible, + All <> units except ''perm'' are compatible, and ''deg'' is their canonical unit. + The permille unit is only valid for angles between -90deg and 90deg, exclusive, + and only really useful between -45deg and 45deg, i.e. -1000perm and 1000perm.
    By convention, @@ -1263,7 +1538,7 @@ Angle Units: the <> type and ''deg'', ''grad'', ''rad'', ''turn'' units -

    -Duration Units: the <

    +Duration units: the <