Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure className bindings work correctly when ShadyDOM.noPatch is… #5518

Merged
merged 9 commits into from
Apr 20, 2019

Conversation

sorvell
Copy link
Contributor

@sorvell sorvell commented Apr 2, 2019

… used.

Puts className on Polymer.dom and ensures any sets to className in the binding system, go through that wrapper.

… used.

Puts `className` on `Polymer.dom` and ensures any sets to `className` in the binding system, go through that wrapper.

Note, depends on webcomponents/shadydom#326.
Copy link
Member

@kevinpschaaf kevinpschaaf left a comment

Choose a reason for hiding this comment

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

LGTM, maybe with a note that noPatch won't be compatible with innerHTML & textContent bindings won't be shady-compatible when in noPatch?

@dfreedm
Copy link
Member

dfreedm commented Apr 10, 2019

Looks like some legit className failure in Chrome 41 and Safari 9

Steven Orvell and others added 4 commits April 11, 2019 10:36
* Ensure `wrap` falls back to using `ShadyDOM.patch` when `noPatch` is not in use so that `className` can be used.
* Ensure `Polymer.dom` uses `patch` when `noPatch` is not in use so that `className` can be used.
@dfreedm dfreedm merged commit 07f1e19 into master Apr 20, 2019
@dfreedm dfreedm deleted the fix-className-bindings-master branch April 20, 2019 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants