Changes between Version 12 and Version 13 of LineBreakingCSS3Mapping

Timestamp:

Aug 31, 2012 9:44:37 PM (12 years ago)

Author:

glenn@skynav.com

Comment:

Add content on after-white-space and migrating to unprefixed line-break.

LineBreakingCSS3Mapping

@@ -136 +136 @@
 == Implementation Details ==
 
- * If `line-break` is `auto`, content language is neither Japanese nor Chinese, and ICU does not provide a tailored set of rules that applies to the content language, then use the **ICU()** column's behavior;
- * If `line-break` is `auto`, content language is neither Japanese nor Chinese, and ICU does provide a tailored set of rules that applies to the content language, then use the **ICU()** column's behavior modulo application of tailored rules;
- * If `line-break` is `auto` and content language is Japanese or Chinese, then use the **Normal(ja)** column's behavior;
- * If `line-break` is `loose` and content language is neither Japanese nor Chinese, then use the **Loose()** column's behavior;
- * If `line-break` is `loose` and content language is Japanese or Chinese, then use the **Loose(ja)** column's behavior;
- * If `line-break` is `normal` and content language is neither Japanese nor Chinese, then use the **Normal()** column's behavior;
- * If `line-break` is `normal` and content language is Japanese or Chinese, then use the **Normal(ja)** column's behavior;
- * If `line-break` is `strict` and content language is neither Japanese nor Chinese, then use the **Strict()** column's behavior;
- * If `line-break` is `strict` and content language is Japanese or Chinese, then use the **Strict(ja)** column's behavior;
+ * If `-webkit-line-break` is `auto`, content language is neither Japanese nor Chinese, and ICU does not provide a tailored set of rules that applies to the content language, then use the **ICU()** column's behavior;
+ * If `-webkit-line-break` is `auto`, content language is neither Japanese nor Chinese, and ICU does provide a tailored set of rules that applies to the content language, then use the **ICU()** column's behavior modulo application of tailored rules;
+ * If `-webkit-line-break` is `auto` and content language is Japanese or Chinese, then use the **Normal(ja)** column's behavior;
+ * If `-webkit-line-break` is `loose` and content language is neither Japanese nor Chinese, then use the **Loose()** column's behavior;
+ * If `-webkit-line-break` is `loose` and content language is Japanese or Chinese, then use the **Loose(ja)** column's behavior;
+ * If `-webkit-line-break` is `normal` and content language is neither Japanese nor Chinese, then use the **Normal()** column's behavior;
+ * If `-webkit-line-break` is `normal` and content language is Japanese or Chinese, then use the **Normal(ja)** column's behavior;
+ * If `-webkit-line-break` is `strict` and content language is neither Japanese nor Chinese, then use the **Strict()** column's behavior;
+ * If `-webkit-line-break` is `strict` and content language is Japanese or Chinese, then use the **Strict(ja)** column's behavior;
+ * If `-webkit-line-break` is `after-white-space`, then use the procedure defined in [#afterWhiteSpace Handling of after-white-space].
 
 For implementation purposes, ''content language'' is determined as described by [http://www.w3.org/TR/html5/global-attributes.html#language to determine the language of a node].
 
 For implementation purposes, ''default line breaking behavior'' is interpreted as the behavior implemented by [http://site.icu-project.org/ ICU] when applying either ICU's default rules or locale specific rules tailored to an identified content language.
+
+=== Handling of `after-white-space` ===
+
+[TBD]
+
+=== Migrating from `-webkit-line-break` to `line-break` ===
+
+When the CSS Working Group designates `line-break` to be unprefixable, it is expected that WebKit will introduce `line-break`, based on but possibly a subset the new `-webkit-line-break` property.