Named entities in attribute values breaks IE syntax #418
Comments
|
Moved detail to ticket created from pull request... sorry for the confusion. |
stepheneb
pushed a commit
to stepheneb/haml
that referenced
this issue
Sep 18, 2011
When attribute values contain both an apostrophe and a double quote, we should substitute the character being used to wrap the value with its key code instead of named/keyword entities (for IE support). Fixes haml#418.
snatchev
pushed a commit
to snatchev/haml
that referenced
this issue
Apr 30, 2012
When attribute values contain both an apostrophe and a double quote, we should substitute the character being used to wrap the value with its key code instead of named/keyword entities (for IE support). Fixes haml#418. Signed-off-by: Norman Clarke <norman@njclarke.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An attribute value is currently replaced with named HTML entities if it has both an apostrophe and a double quote:
%div{"data-props" => "someJsValue: 'has a \"something quoted\" in it'"}becomes:
<div data-props="someJsValue: 'has a "something quoted" in it'"></div>This is fine for sane browsers, but IE deems it is a syntax error. All browsers, however, can handle using key character codes:
<div data-props="someJsValue: 'has a "something quoted" in it'"></div>Other than punishing those who must support IE, is there any reason for not changing this?
The text was updated successfully, but these errors were encountered: