Platform/Features/Vertical text - Revision history

Fantasai at 08:24, 24 May 2013

2013-05-24T08:24:02Z

← Older revision		Revision as of 08:24, 24 May 2013
Line 35:		Line 35:
	* Support vertical text in SVG		* Support vertical text in SVG
	\|Feature functional spec=* Bug 0 - Prototype		\|Feature functional spec=* Bug 0 - Prototype
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2] - Parse writing mode and ~~direction~~		* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 1] - Parse writing mode and text-orientation
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1] - Logicalize		* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 2] - Logicalize Reflow APIs
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3] - ~~Layout~~		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3] - Logicalize Reflow for all frame classes
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=649142 ~~refactor~~] and extend logical CSS properties		* [https://bugzilla.mozilla.org/show_bug.cgi?id=649142 Bug 4] - Refactor and extend logical CSS properties
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4] - Orthogonal Flows		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4] - Orthogonal Flows
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5] - UI		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5] - UI
Line 47:		Line 47:
	** Glyph layout of CJK only		** Glyph layout of CJK only
	** Parsing, orthogonal flows and UI will not be included		** Parsing, orthogonal flows and UI will not be included
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1]: Logicalization of layout parameters		* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2]: Parsing of <code>writing-mode</code> and <code>text-orientation</code><br>(see [[#9._Implementation\|Implementation]] below)
	** ~~Renaming~~
	** ~~really want~~ to ~~do this a class at a time~~, ~~alternating with bug~~ 3~~, to check that it's being done right~~		The above is done. Steps to implement (parallelizable steps preceded by --> to indicate possible forking-off):

			* --> [https://bugzilla.mozilla.org/show_bug.cgi?id=649142 Bug 4] - Refactor existing logical CSS properties
			* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 1] - Parse writing mode and text-orientation
			* --> Extend logical CSS properties to handle vertical text (depends only on Bugs 1 and 4)
			* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 2]: Logicalization of layout parameters
			** May involve some renaming across the layout engine, but shouldn't affect logic at this point
			** Note that some frame classes will continue to be physical, e.g. images, even after full logicalization
			* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3]: Logicalize Block and Inline layout
			** Logicalize nsBlockFrame. Get vertical-only/horizontal-only documents consisting of only block frames working/tested
	** 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~~		** Logicalize nsLineLayout, nsInlineFrame, nsTextFrame, etc. Get inline layout working for vertical-only documents. Make the text just draw sideways for now.
	* ~~[https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2]: Parsing of <code>writing~~-~~mode</code~~> and ~~<code>text-orientation</code><br>(see [[#9~~.~~_Implementation\|Implementation]] below)~~		* --> After block and inline layout, other frame classes can be converted set by set, e.g.
	* ~~[https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3]: Layout~~		** Tables
	** i.~~e., in a document with a vertical writing mode, laying out the whole document with a horizontal block flow and vertical text flow~~		** Flexbox
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4]: Orthogonal flows~~<br>[http://unicode~~.~~org/notes/tn22/RobustVerticalLayout.pdf Unicode Technical Note #22]~~		** etc.
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5]: UI features		* --> [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4]: Orthogonal flows
			** Probably requires a lot of rework of intrinsic sizing. This is a complicated task!
			* --> [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5]: UI features
	** scrollbars		** scrollbars
	** mapping scrollwheel		** mapping scrollwheel
Line 62:		Line 73:
	** vertical text selection cursor		** vertical text selection cursor
	** caret browsing		** caret browsing
	** list boxes/combo boxes		** list boxes/combo boxes (initial implementation should just transform the control; next pass does actual vertical layout)
	** menus		** menus
	** other?		** other?
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789104 Bug 6]: Glyph orientation		* --> [https://bugzilla.mozilla.org/show_bug.cgi?id=789104 Bug 6]: Glyph orientation
	** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/ UTR-50] (currently under review)		** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/ UTR-50] (currently under review)
	** Supporting different modes as necessary (e.g. stacked vs default, cf. <code>text-orientation</code> which is in flux)		** Supporting different modes as necessary (e.g. stacked vs default, cf. <code>text-orientation</code> which is in flux)
Line 73:		Line 84:

	* Need to investigate how to pref CSS keyword parsing (and all writing-mode processing) on and off. (This is relatively straightforward, now that {{bug\|753522}} is implemented. Just specify the pref in the property's chunk of nsCSSPropList.h, and use Preferences::GetBool() elsewhere if necessary.)		* Need to investigate how to pref CSS keyword parsing (and all writing-mode processing) on and off. (This is relatively straightforward, now that {{bug\|753522}} is implemented. Just specify the pref in the property's chunk of nsCSSPropList.h, and use Preferences::GetBool() elsewhere if necessary.)
	* 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?		* 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? [There shouldn't be any perf cost.]

	* Multi-column vertical layout		* Multi-column vertical layout

Dbaron: more bugs

2013-05-23T07:58:28Z

more bugs

← Older revision		Revision as of 07:58, 23 May 2013
Line 35:		Line 35:
	* Support vertical text in SVG		* Support vertical text in SVG
	\|Feature functional spec=* Bug 0 - Prototype		\|Feature functional spec=* Bug 0 - Prototype
			* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2] - Parse writing mode and direction
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1] - Logicalize		* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1] - Logicalize
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2] - Parse
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3] - Layout		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3] - Layout
			* [https://bugzilla.mozilla.org/show_bug.cgi?id=649142 refactor] and extend logical CSS properties
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4] - Orthogonal Flows		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4] - Orthogonal Flows
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5] - UI		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5] - UI

Dbaron: 1 alternates with 3 (after 2)

2013-05-23T07:56:49Z

1 alternates with 3 (after 2)

← Older revision		Revision as of 07:56, 23 May 2013
Line 48:		Line 48:
	* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1]: Logicalization of layout parameters		* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1]: Logicalization of layout parameters
	** Renaming		** Renaming
			** really want to do this a class at a time, alternating with bug 3, to check that it's being done right
	** 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

Dholbert: Note that we don't need separate IDLs to get preffable CSS properties.

2013-05-23T07:34:04Z

Note that we don't need separate IDLs to get preffable CSS properties.

← Older revision		Revision as of 07:34, 23 May 2013
Line 70:		Line 70:
	\|Feature implementation notes=[https://bugzilla.mozilla.org/show_bug.cgi?id=145503 Main bugzilla entry]		\|Feature implementation notes=[https://bugzilla.mozilla.org/show_bug.cgi?id=145503 Main bugzilla entry]

	* Need to investigate how to pref CSS keyword parsing (and all writing-mode processing) on and off ~~-- put~~ in ~~a separate DOM idl?~~		* Need to investigate how to pref CSS keyword parsing (and all writing-mode processing) on and off. (This is relatively straightforward, now that {{bug\|753522}} is implemented. Just specify the pref in the property's chunk of nsCSSPropList.h, and use Preferences::GetBool() elsewhere if necessary.)
	* 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?		* 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?

Smontagu at 17:09, 6 September 2012

2012-09-06T17:09:44Z

← Older revision		Revision as of 17:09, 6 September 2012
Line 35:		Line 35:
	* Support vertical text in SVG		* Support vertical text in SVG
	\|Feature functional spec=* Bug 0 - Prototype		\|Feature functional spec=* Bug 0 - Prototype
	* Bug 1 - Logicalize		* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 Bug 1] - Logicalize
	* Bug 2 - Parse		* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2] - Parse
	* Bug 3 - Layout		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3] - Layout
	* Bug 4 - Orthogonal Flows		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4] - Orthogonal Flows
	* Bug 5 - UI		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5] - UI
	* Bug 6 - Text/Glyph Layout		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789104 Bug 6] - Text/Glyph Layout
	\|Feature implementation plan=* Prototype of a vertical text layout. This will include:		\|Feature implementation plan=* Prototype of a vertical text layout. This will include:
	** logicalization of a minimum of frame types		** logicalization of a minimum of frame types
Line 46:		Line 46:
	** Glyph layout of CJK only		** Glyph layout of CJK only
	** Parsing, orthogonal flows and UI will not be included		** Parsing, orthogonal flows and UI will not be included
	* Bug 1: Logicalization of layout parameters		* [https://bugzilla.mozilla.org/show_bug.cgi?id=735577 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
	* Bug 2: Parsing of <code>writing-mode</code> and <code>text-orientation</code><br>(see [[#9._Implementation\|Implementation]] below)		* [https://bugzilla.mozilla.org/show_bug.cgi?id=772321 Bug 2]: Parsing of <code>writing-mode</code> and <code>text-orientation</code><br>(see [[#9._Implementation\|Implementation]] below)
	* Bug 3: Layout		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789096 Bug 3]: Layout
	** i.e., in a document with a vertical writing mode, laying out the whole document with a horizontal block flow and vertical text flow		** i.e., in a document with a vertical writing mode, laying out the whole document with a horizontal block flow and vertical text flow
	* Bug 4: Orthogonal flows<br>[http://unicode.org/notes/tn22/RobustVerticalLayout.pdf Unicode Technical Note #22]		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789099 Bug 4]: Orthogonal flows<br>[http://unicode.org/notes/tn22/RobustVerticalLayout.pdf Unicode Technical Note #22]
	* Bug 5: UI features		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789103 Bug 5]: UI features
	** scrollbars		** scrollbars
	** mapping scrollwheel		** mapping scrollwheel
Line 60:		Line 60:
	** vertical text selection cursor		** vertical text selection cursor
	** caret browsing		** caret browsing
	** ~~UI widgets~~		** list boxes/combo boxes
			** menus
	** other?		** other?
	* Glyph orientation		* [https://bugzilla.mozilla.org/show_bug.cgi?id=789104 Bug 6]: Glyph orientation
	** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/ UTR-50] (currently under review)		** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/ UTR-50] (currently under review)
	** Supporting different modes as necessary (e.g. stacked vs default, cf. <code>text-orientation</code> which is in flux)		** Supporting different modes as necessary (e.g. stacked vs default, cf. <code>text-orientation</code> which is in flux)

Smontagu at 16:39, 6 September 2012

2012-09-06T16:39:17Z

← Older revision		Revision as of 16:39, 6 September 2012
Line 41:		Line 41:
	* Bug 5 - UI		* Bug 5 - UI
	* 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:
	This will include:
	** logicalization of a minimum of frame types		** logicalization of a minimum of frame types
	** layout of a minimum of frame types		** layout of a minimum of frame types
	** Glyph layout of CJK only		** Glyph layout of CJK only
	** Parsing, orthogonal flows and UI will not be included		** Parsing, orthogonal flows and UI will not be included

	* Bug 1: Logicalization of layout parameters		* 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
	* Bug 2: Parsing of <code>writing-mode</code> and <code>text-orientation</code>		* Bug 2: Parsing of <code>writing-mode</code> and <code>text-orientation</code><br>(see [[#9._Implementation\|Implementation]] below)
	(see [[#Implementation~~\|implementation notes~~]] below)		* Bug 3: Layout
	* ~~Initial containing block with a vertical writing mode~~		** i.e., in a document with a vertical writing mode, 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		* Bug 4: Orthogonal flows<br>[http://unicode.org/notes/tn22/RobustVerticalLayout.pdf Unicode Technical Note #22]
	** UI features		* Bug 5: UI features
	*** scrollbars		** scrollbars
	*** mapping scrollwheel		** mapping scrollwheel
	*** vertical text selection		** vertical text selection
	*** vertical text selection cursor		** vertical text selection cursor
	*** caret browsing		** caret browsing
	*** other?		** UI widgets
	* ~~Implement~~ <code>~~min/max/fit~~-~~content~~</code>, <code>~~fill-available~~</code>		** other?
	* Orthogonal flows		* Glyph orientation
			** Using character properties such as those defined in [http://www.unicode.org/reports/tr50/ UTR-50] (currently under review)
			** Supporting different modes as necessary (e.g. stacked vs default, cf. <code>text-orientation</code> which is in flux)
			** Glyph selection—choosing vertical variants, using vertical metrics
			** OpenType model for vertical text needs to be flushed out a bit more (e.g. which features are on by default in the vertical case?)
			\|Feature implementation notes=[https://bugzilla.mozilla.org/show_bug.cgi?id=145503 Main bugzilla entry]

			* 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?

	* Multi-column vertical layout		* Multi-column vertical layout
	* Form controls		* Form controls
Line 70:		Line 77:
	* (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?)		* (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~~		* Implement <code>min/max/fit-content</code>, <code>fill-available</code>
	** Using character properties such as those defined in [http://~~www.unicode.org~~/~~reports/tr50/ UTR-50] (currently under review)~~
	** Supporting different modes as necessary (e.g. stacked vs default, ~~cf.~~ <code>~~text~~-~~orientation~~</code> ~~which is in flux)~~
	* Glyph selection—choosing vertical variants, using vertical metrics
	* OpenType model for vertical text needs to be flushed out a bit more (e.g. which features are on by default in the vertical case?)
	~~\|Feature implementation notes=[https://bugzilla.mozilla.org/show_bug.cgi?id=145503 Main bugzilla entry]~~
	}}		}}
	{{FeatureInfo		{{FeatureInfo
Line 82:		Line 84:
	\|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?
	}}

Smontagu at 16:28, 6 September 2012

2012-09-06T16:28:47Z

← Older revision		Revision as of 16:28, 6 September 2012
Line 53:		Line 53:
	** Get all tests to pass with logical params in use		** Get all tests to pass with logical params in use
	* Bug 2: 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 [#Implementation implementation notes] below)		(see [[#Implementation\|implementation 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

Smontagu at 16:20, 6 September 2012

2012-09-06T16:20:14Z

← Older revision		Revision as of 16:20, 6 September 2012
Line 53:		Line 53:
	** Get all tests to pass with logical params in use		** Get all tests to pass with logical params in use
	* Bug 2: 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)		(see [#Implementation implementation 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 83:		Line 83:
	}}		}}
	{{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?		\|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?		* 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?
	}}		}}

Smontagu at 16:15, 6 September 2012

2012-09-06T16:15:56Z

← Older revision		Revision as of 16:15, 6 September 2012
Line 53:		Line 53:
	** Get all tests to pass with logical params in use		** Get all tests to pass with logical params in use
	* Bug 2: 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)		(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

Smontagu at 16:13, 6 September 2012

2012-09-06T16:13:53Z

← Older revision		Revision as of 16:13, 6 September 2012
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

	~~Some of the work items~~:		* Bug 1: Logicalization of layout parameters
	* 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>
	** Need to investigate how to pref this (~~and all writing-mode processing~~) ~~on and off -- put in a separate DOM idl?~~		(see [Engineering notes:engineering notes] below)
	** 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?
	* 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?
			}}