Skip to content

Conversation

@sophiebits
Copy link
Collaborator

The attribute was getting set in the HTML before but not in createElement mode since we were mocking out the setter, causing divergent behavior. Maybe I should've done a getOwnPropertyDescriptor and wrapped it.

The attribute was getting set in the HTML before but not in createElement mode since we were mocking out the setter, causing divergent behavior. Maybe I should've done a `getOwnPropertyDescriptor` and wrapped it.
@sophiebits sophiebits added this to the 15.0 milestone Apr 6, 2016
return nodeValue;
},
set: nodeValueSetter.mockImplementation(function(newValue) {
node.setAttribute('value', newValue);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Said offline but the DOM doesn't do this so while it tricks the test it's not real life.

@sophiebits
Copy link
Collaborator Author

Blargh. #6426

@sophiebits sophiebits closed this Apr 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants