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 Feb 9, 2024. It is now read-only.
In my current project I'm looking to get a table from an external javascript file that contains a document.write. In the past we've done that in this fashion:
Angular2 removes script tags from templates, so that is not a solution. I've used postscribe and that worked when Angular2 was still in RCs. At some point I suddenly noticed it stopped working, and can't trace back what package broke it.
I now get this error:
The afterWrite callback still fires and the document.write in the external JS file has been written, but the done callback won't fire anymore. Since I'm working with an Angular2 SPA, the postscribe call won't happen again when opening a similar page, since it produced an error.
I've tried many things, but simply don't know what causes this. Was hoping anyone could help.
Using Postscribe in combination with Angular2.
In my current project I'm looking to get a table from an external javascript file that contains a document.write. In the past we've done that in this fashion:
Angular2 removes script tags from templates, so that is not a solution. I've used postscribe and that worked when Angular2 was still in RCs. At some point I suddenly noticed it stopped working, and can't trace back what package broke it.
I now get this error:
The afterWrite callback still fires and the document.write in the external JS file has been written, but the done callback won't fire anymore. Since I'm working with an Angular2 SPA, the postscribe call won't happen again when opening a similar page, since it produced an error.
I've tried many things, but simply don't know what causes this. Was hoping anyone could help.
Plunkr: http://plnkr.co/edit/FHSVKDL2rv8TAQyTeqE2?p=preview
You can see it's working, but in the console you see the same errors described above.
The text was updated successfully, but these errors were encountered: