id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
4229	CSS selector support for Test Environment	Tobiasz Cudnik		"CSS selector support for Test Environment would bring us such benefits for node-related TCs:
 * shorter, leaner, more readable TCs
 * less time needed to implement a TC
 * more general node-access code formulas (possibly reusable)

""Node-related"" TCs means any operation which operates on specific nodes (in both forms - as plain text and DOM representations) which are placed in larger set of other nodes. This can include things like:
 * click specific button
 * check if results inside editor is the desired one
 * add new markup in specific place

Possible solutions for this could be provided by:
 * [http://sizzlejs.com/ sizzle]
 * [http://www.domassistant.com/ DOM Assistant]
 * [http://www.prototypejs.org/ prototype] (which ships with CKTester from #4218)
 * [http://developer.yahoo.com/yui/selector/ YUI selector] (which could share it's core with YUI tests)
 * [http://www.dojotoolkit.org/ dojo.query]

One popular selector benchmark is [http://mootools.net/slickspeed/ slickspeed] (although speed isn't out concern).

I think that most important factors when making a decision are (for us):
 * size of additional code
 * stability across all browser (including IE6) in dangerous TC environment
 * support level"	New Feature	closed	Normal		QA		fixed	Discussion