67
edits
Platform/Features/Vertical text: Difference between revisions
Jump to navigation
Jump to search
Platform/Features/Vertical text (view source)
Revision as of 16:13, 6 September 2012
, 6 September 2012no edit summary
Jetvillegas (talk | contribs) No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
* Bug 6 - Text/Glyph Layout | * Bug 6 - Text/Glyph Layout | ||
|Feature implementation plan=* Prototype of a vertical text layout | |Feature implementation plan=* Prototype of a vertical text layout | ||
This will include: | |||
** logicalization of a minimum of frame types | |||
** layout of a minimum of frame types | |||
** Glyph layout of CJK only | |||
** Parsing, orthogonal flows and UI will not be included | |||
* Bug 1: Logicalization of layout parameters | |||
** Renaming | ** 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. | ** 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 | ** Get all tests to pass with logical params in use | ||
* Parsing of <code>writing-mode</code> and <code>text-orientation</code> | * Bug 2: Parsing of <code>writing-mode</code> and <code>text-orientation</code> | ||
(see [Engineering notes:engineering notes] below) | |||
* Initial containing block with a vertical writing mode | * Initial containing block with a vertical writing mode | ||
** i.e. laying out the whole document with a horizontal block flow and vertical text flow | ** i.e. laying out the whole document with a horizontal block flow and vertical text flow | ||
| Line 79: | Line 82: | ||
|Feature engineering team=Layout | |Feature engineering team=Layout | ||
}} | }} | ||
{{FeatureTeamStatus}} | {{FeatureTeamStatus | ||
|Feature engineering notes=** Need to investigate how to pref CSS keyword parsing (and all writing-mode processing) on and off -- put in a separate DOM idl? | |||
** 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? | |||
}} | |||