Skip to content
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.

IE10 sanitizes a bunch of content attribute values #110

Closed
rafaelw opened this issue Jun 20, 2013 · 5 comments
Closed

IE10 sanitizes a bunch of content attribute values #110

rafaelw opened this issue Jun 20, 2013 · 5 comments

Comments

@rafaelw
Copy link
Contributor

rafaelw commented Jun 20, 2013

e.g.

var elmName, attrName;
var el = document.createElement(elmName);
el.setAttribute(attrName, '{{ foo }}');
alert(el.getAttribute(attrName)); // alerts 'null' in IE, but '{{ foo }}' in Gecko/WK/Blink.

E.g. elmName/attrName =
input[type='number'] / value

  • / style

Hixie says content attributes should never be sanitized. IE apparently disagrees.

Sad clown.

@arv
Copy link
Contributor

arv commented Jun 21, 2013

Clearly an IE bug

@rafaelw
Copy link
Contributor Author

rafaelw commented Jun 21, 2013

Yes, but we still need to work in IE. I propose that when template finds, e.g.

<div _foo="{{ bar }}">

that it acts as if it had seen

<div foo="{{ bar }}">

This should cover the case of IE sanitizing attributes, as well as the issue of non-template browsers lacking inert content (e.g. <img _src="{{ foo }}.png">

@neonstalwart
Copy link

@rafaelw some of your comments don't seem to come through on github - maybe you need to use fenced code blocks

@rafaelw
Copy link
Contributor Author

rafaelw commented Jun 22, 2013

sorry. fixed.

@rafaelw
Copy link
Contributor Author

rafaelw commented Oct 23, 2013

Fixed: 3932ebe

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants