jQuery out of policy error
Isn't it the purpose of JQuery make life easier and more productive?
To me the very main principal reason of Jquery core is solving problems about compatibility, but of course there is much more in it than that.
Based on this, I agree if JQuery in some cases needs to make some things , lets say, more complex or difficult to code in pro of the compatibility, but ... (now the case)
Why this rule?
If you wish to use any of the meta-characters ( such as !"#$%&'()*+,./:;?@[\]`{|}~ ) as a literal part of a name, you must escape the character with two backslashes
I see there many symbols out of context respect to the id attribute specific standards, but is ok
but why not to respect the standards?
Why you can't use a semicolon as it is in an id="dct:ref"
Why the need to escape it? It should not be that way, for other characters or symbols out of the standar, ok, but for what is defined in the standard there should not be any special rule.
And... byt he way, tested and in fact even usign the double slash it does not works
Is it that difficult to read the colon in an id to follow the standars?
There are many many reports since years ago about that coding problem in the tickets, and nobody as done anything about it, just mark it as invalid and responding with something which is not the right answer
So if the principle of using jQuery is a workaround incompatibilities
now the use of
$('[id="test:two"]')
or
$('#test\\:two')
instead of
$('#test:two')
Is jQuery starting to play the same role as browser have,
getting version with version more capable, more complex
but messing up, evading responsabilities.
Thanks