You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.
When surfing the web while this chrome extensionis active I get a white page and the following result in console:
Uncaught TypeError: fnRef.apply is not a function polydev/vendor/zone-microtask.js:406
fnNames.map.forEach.global.zone.(anonymous function).arguments.(anonymous function) @ polydev/vendor/zone-microtask.js:406
(anonymous function) @ polydev/vendor/zone-microtask.js:98
run @ polydev/vendor/zone-microtask.js:118
zoneBoundFn @ polydev/vendor/zone-microtask.js:91
The page causing this is a login success page and not using polymer at all. It's using a form and javascript to forward a security token to another page. The important parts look like this:
Using a breakpoint in zone-microtask:406 you can see that the apply is called on "document.forms[0].submit()"
Is this bug caused by window.setTimeout(...)?
The text was updated successfully, but these errors were encountered:
When surfing the web while this chrome extensionis active I get a white page and the following result in console:
Uncaught TypeError: fnRef.apply is not a function polydev/vendor/zone-microtask.js:406
fnNames.map.forEach.global.zone.(anonymous function).arguments.(anonymous function) @ polydev/vendor/zone-microtask.js:406
(anonymous function) @ polydev/vendor/zone-microtask.js:98
run @ polydev/vendor/zone-microtask.js:118
zoneBoundFn @ polydev/vendor/zone-microtask.js:91
The page causing this is a login success page and not using polymer at all. It's using a form and javascript to forward a security token to another page. The important parts look like this:
(The sensitive values have been replaced by ...)
Using a breakpoint in zone-microtask:406 you can see that the apply is called on "document.forms[0].submit()"
Is this bug caused by window.setTimeout(...)?
The text was updated successfully, but these errors were encountered: