Jonathan Griffin (:jgriffin) Reporter
	Description • 15 years ago

We have a number of mochitests that test things by enabling the HTML5 pref (html5.enable), and then running a test.  Once the HTML5 parser is enabled by default, these tests should be updated to remove this code.

	Jeff Walden [:Waldo]
	Comment 1 • 15 years ago

Bugs on particular Mochitests, even when those particular tests constitute large swaths, go in a component relevant to the function being tested.

	Jonathan Griffin (:jgriffin) Reporter
	Comment 2 • 14 years ago

Henri, since HTML5 is enabled by default, is it safe (on trunk) to remove the code from the html5 tree-construction tests that sets the html5.enable preference?

	Henri Sivonen (:hsivonen) (away from Bugzilla until 2023-09-11)
	Comment 3 • 14 years ago

Oops. Sorry about my failure to respond earlier.

Earlier, the plan was to keep the option to go back to the old HTML parser as a contingency plan. However, now new work has been done that depends on the capabilities of the HTML5 parser.

smaug, Does your work on bug 462076 and 562013 make it infeasible to keep supporting html5.enable=false?

jst, What's your take on making test suites explicitly no longer support html5.enable=false?

	Jonathan Griffin (:jgriffin) Reporter
	Comment 4 • 11 years ago

obsolete