Platform/Features/Vertical text: Difference between revisions

Platform/Features/Vertical text (view source)

Revision as of 05:04, 13 March 2012

86 bytes added , 13 March 2012

Revise work items list based on discussion with dbaron, bz, sjohnson, fantasai

Brian

Confirmed users

166

edits

@@ Line 24: / Line 24: @@
 * Support [https://bugzilla.mozilla.org/show_bug.cgi?id=33339 HTML ruby]
 * Support vertical text in SVG
-|Feature implementation plan=Some ''very rough'' ideas of ''some'' of the work items (this is likely to be '''very''' wrong):
+|Feature implementation plan=Some of the work items:
+* Logicalization of layout parameters
+** Renaming
+** Note that not all properties get treated the same. For example, the offset of a <code>text-shadow</code> property is unaffected by writing mode.
+** Get all tests to pass with logical params in use
 * Parsing of <code>writing-mode</code> and <code>text-orientation</code>
-* Virtualizing layout parameters???
+** Need to investigate how to pref this (and all writing-mode processing) on and off -- put in a separate DOM idl?
-** e.g. there was a suggestion of making a subclass of nsMargin that also referred to the current writing mode to give you the "logical" equivalents such as "before" and "after" instead of "top" and "bottom". Is this the approach we want to follow? Same goes for padding, borders etc.
+** Possibly want to be able to <code>#ifdef</code> it as well? Or just back out the changes after each uplift so we don't pay the perf cost until it's ready?
-** Note that not all properties get treated the same. For example, the offset of a <code>text-shadow</code> property is unaffected by writing mode.
 * ICB with a vertical writing mode
 ** i.e. laying out the whole document with a horizontal block flow and vertical text flow
-** UI adjustments (e.g. horizontal scrollbar, mapping scrollwheel, vertical text selection cursor etc.)
+** UI features
+*** scrollbars
+*** mapping scrollwheel
+*** vertical text selection
+*** vertical text selection cursor
+*** caret browsing
+*** other?
+* Implement <code>min/max/fit-content</code>, <code>fill-available</code>
 * Orthogonal flows
 * Multi-column vertical layout
-* Vertical form controls??
+* Form controls
 * Tables
 * (Probably lots of other HTML elements that require special handling? e.g. list markers. Presumably images don't rotate (i.e. width/height are physical) but form controls do?)
-* Pagination?
+* Pagination
 * Glyph orientation
 ** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/tr50-3.html UTR-50] (or the [http://www.unicode.org/~iancu/12102-update-utr50.pdf updated proposal to revise UTR-50])