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

Cannot assign to read only property 'target' of object '#<AnimationPlaybackEvent>' #229

Closed
1 of 8 tasks
govis opened this issue Apr 13, 2017 · 8 comments
Closed
1 of 8 tasks
Assignees

Comments

@govis
Copy link

govis commented Apr 13, 2017

Description

All Demos yield a Cannot assign to read only property 'target' of object '#<AnimationPlaybackEvent>' error coming from https://github.com/web-animations/web-animations-js/blob/master/src/web-animations-next-animation.js#L223

neon-animation v2.0.0 (2.0-preview)
web-animations-js v2.2.3
polymer v2.0.0-rc.4
webcomponentsjs v1.0.0-rc.8

Expected outcome

No errors

Actual outcome

Cannot assign to read only property 'target' of object '#'" error

Live Demo

Run any of the demos:

image

Browsers Affected

  • Chrome
  • Firefox
  • Safari 9
  • Safari 8
  • Safari 7
  • Edge
  • IE 11
  • IE 10
@govis
Copy link
Author

govis commented Apr 13, 2017

Looks like it has something to do with the 2.2.3 commit in web-animations/web-animations-js: web-animations/web-animations-js#123

@krumware
Copy link

Getting the same issue over here. neon-animation references web-animations-js version 2.2.0, but version 2.2.3 is the actual version being pulled. 2.2.0 is not an available release tag in web-animations-js https://github.com/web-animations/web-animations-js/releases

@krumware
Copy link

Also, I wanted to clarify, the issue here references Polymer 2.0+, but we are seeing the same issue on Polymer 1.8.1

@krumware
Copy link

krumware commented Apr 13, 2017

our temporary fix was to add the following to our app's bower.json
"web-animations-js": "web-animations/web-animations-js#2.2.2"

@fungusamongus
Copy link

We also had this problem in one of our polymer projects and fixed it by setting the specific 2.2.2 tag in our bower. This is with Polymer 1.8.1

krumware added a commit to krumware/neon-animation that referenced this issue Apr 13, 2017
web-animations-js version 2.2.3 is broken.
Resolves PolymerElements#229
@samuelli samuelli self-assigned this Apr 13, 2017
@samuelli
Copy link
Member

Just to keep everyone in the loop. I'm trying to get this fixed upstream in web-animations. If that doesn't resolve in the next few hours, we'll go with this stop-gap solution in #230

@krumware
Copy link

krumware commented Apr 13, 2017 via email

@samuelli
Copy link
Member

Thanks for your patience. This has been fixed upstream in web-animations/web-animations-js#124. Please update to v2.2.4 for web-animations-js and the issue should be resolved.

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

No branches or pull requests

4 participants