Attribute values are not decoded for escape characters. This may or may not be important depending on the types of the attribute. The only real issue here is that it means you can't use ) in attribute values.
name and ID are not a problem, since ) is not a name character.
for language it could technically be a problem, but it is hard to think of an instance.
for condition expressions, the inability to use parens could be an issue. But how big an issue is it really? There are obvious workarounds using other brackets, and who would want to have to use escaped parens in their condition expressions.
The other issue would be the desire to use character entities for accented characters. But people who need to enter such characters regularly presumably have keyboard ways of entering them as unicode characters.
So far, then, I don't think this is much of an issue. On the other hand, I'm not sure there is much of a downside to supporting escapes either, for the sake of uniformity.
Attribute values are not decoded for escape characters. This may or may not be important depending on the types of the attribute. The only real issue here is that it means you can't use
)
in attribute values.name and ID are not a problem, since
)
is not a name character.for language it could technically be a problem, but it is hard to think of an instance.
for condition expressions, the inability to use parens could be an issue. But how big an issue is it really? There are obvious workarounds using other brackets, and who would want to have to use escaped parens in their condition expressions.
The other issue would be the desire to use character entities for accented characters. But people who need to enter such characters regularly presumably have keyboard ways of entering them as unicode characters.
So far, then, I don't think this is much of an issue. On the other hand, I'm not sure there is much of a downside to supporting escapes either, for the sake of uniformity.