Context Navigation

Changes between Initial Version and Version 1 of Ticket #11415, comment 1

initial	v1
1	1	As a thought exercise, if it were Chrome or Firefox that was picky would you want this behavior? Is IE wrong about the error or is the code wrong in a possibly-benign way and other browsers ignored it?
2	2
3		With `.css("border: 1px 1px -1px 4px")`, are we supposed to parse the shorthand property and look for negative numbers? A more horrifying fix IMO would be to wrap it all in a try/catch and ignore any hint of an error coming out of the property assignment.
	3	With `.css("border", "1px 1px -1px 4px")`, are we supposed to parse the shorthand property and look for negative numbers? A more horrifying fix IMO would be to wrap it all in a try/catch and ignore any hint of an error coming out of the property assignment.
4	4
5	5	I think our goals for cross-browser consistency should cover valid inputs, not invalid ones. Invalid inputs are errors and should be fixed.