Skip to content
This repository was archived by the owner on Feb 22, 2018. It is now read-only.

shadow_dom_components example crashing in Firefox #1337

Closed
Pajn opened this issue Aug 10, 2014 · 9 comments
Closed

shadow_dom_components example crashing in Firefox #1337

Pajn opened this issue Aug 10, 2014 · 9 comments

Comments

@Pajn
Copy link

Pajn commented Aug 10, 2014

After compiling the shadow_dom_components example and running it in Firefox it crashes with this printout in the console:

"[Exception... "Illegal operation on WrappedNative prototype object"  nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)"  location: "JS frame :: http://127.0.0.1:8080/shadow_dom_components.dart.js :: .lookupAndCacheInterceptor :: line 3298"  data: no]

STACKTRACE:
"

This happens with both Dart stable and dev releases with Angulars master (commit 3ec5d75)

@vicb
Copy link
Contributor

vicb commented Aug 29, 2014

Does this still happen on the latest master ?

@Pajn
Copy link
Author

Pajn commented Aug 30, 2014

Yes

This can be seen in the Travis builds too https://travis-ci.org/angular/angular.dart/jobs/33940103#L1297
however, the tests still passes which is a bit strange.

@vicb
Copy link
Contributor

vicb commented Sep 1, 2014

@vsavkin do you work on this ?

@vsavkin
Copy link
Contributor

vsavkin commented Sep 1, 2014

@Pajn I believe an old version the web_components package causes the crash. I tried the example app with web_components 0.6.0+1 and it worked fine. Can you try to upgrade the package?

@vsavkin
Copy link
Contributor

vsavkin commented Sep 1, 2014

@vicb no, I am working on transcluding components.

@vicb
Copy link
Contributor

vicb commented Sep 1, 2014

@vsavkin Thanks for the update. Upgrading wc would be an easy fix, @Pajn could you please try with the latest 5.x and 6.x versions an report the result ?

(edit: We need to test with the latest 5.x to have the largest possible version constraint)

@Pajn
Copy link
Author

Pajn commented Sep 2, 2014

Both 0.5.0+1 and 0.6.0+1 works, however the version 0.3.3 specified in the lockfile doesn't (which means that just a pub get will crash and pub upgrade needs to be run).
I don't know if this is fixed with just a updated lockfile or if a version constraint also should be specified in the pubspec.yaml file.

@vicb
Copy link
Contributor

vicb commented Sep 4, 2014

There is not question whether the lock file must be updated.

I would also like to have the constraint added the yaml file, @jbdeboer what do you think ?

@rkirov
Copy link
Contributor

rkirov commented Oct 9, 2014

Can't reproduce.

@rkirov rkirov closed this as completed Oct 9, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

4 participants