I didn't say not to test. I said not to test only on a single browser version.
> Says who?
Do you really need a list?
> when the tests themselves aren't pinned down
Test for compliance with the standard, not compatibility with the engine. If not enough engines support a feature for which the standard is still emerging don't use it.
> We have even given direct examples, such as Google's decision to kill H.264 support in Chrome.
Your examples don't hold water. No specific codec support should be assumed at this point because it's not standardised.
> Says who?
Do you really need a list?
> when the tests themselves aren't pinned down
Test for compliance with the standard, not compatibility with the engine. If not enough engines support a feature for which the standard is still emerging don't use it.
> We have even given direct examples, such as Google's decision to kill H.264 support in Chrome.
Your examples don't hold water. No specific codec support should be assumed at this point because it's not standardised.