I have adopted the pdfmake.js library into my angular js project for generating PDF's.Its implemented well and works very fine with google chrome(all versions) and mozilla(only some versions).
In mozilla latest version (50.0.0),can't generate Pdf. and there is no error in the console. I have searched long time for the solution of this problem.
I couldn't find out and couldn't fix my self.
If any one encountered this problem and know the solution of this issue, please just share it with me.
I was going through same issue. this is the issue is related with the version of pdfmake you are usng.
Try this version.
It is more stable and performance wise its much more better.
Related
We are using this package with ReactJS. This is working as per expectation in all browsers except Firefox. When the user interacts to download the PDF, Firefox hangs completely, and show attached message.Memory usage looks fine.
Screenshot of Browser Message:
Are you trying dynamic import by any chance?
As according to me, If I understood your question, it seems like its a module issue that you are using, because it's an open issue not Fixed yet.
(description link:https://github.com/eKoopmans/html2pdf/issues/45 )
You can use some other popular library like react-pdf, PDFKit, pdfshift.
Hopefully, this can solve your issue.
My problem may seem a bit vague (it is to me too), but here is my attempted explanation of it.
A few months ago, I implemented PDF.js in my web application. It was really useful, and I am using it for interactions with my clients.
Suddenly, last week, my clients reported to me "Aw, Snap" messages in Google Chrome on their PCs when they try to launch PDF.js. I have an iMac and two PCs at home, so I decided to test this out.
When I used Google Chrome on my iMac to launch PDF.js, I found it worked fine.
When I used Google Chrome on my first PC to launch PDF.js, I found it worked fine.
When I used Google Chrome on my second PC to launch PDF.js, even though it previously worked, it kept crashing and showing me "Aw, Snap" messages.
This was weird. I tried removing all the extensions, clearing the cache, clearing the LocalStorage, but nothing seemed to fix the problem.
I then realised, after some communication with my clients, launching PDF.js in Safari, Torch, Opera or Firefox on any operating system worked perfectly fine.
Why would this happen? I am using the web viewer in PDF.js. I also tried with the basic hello world example, but that broke as well (which I now find really weird), so I suspect there's something wrong with the rendering engine.
I also tried including the compatibility.js file after building the source, but with no avail.
Is there any known bug which causes Google Chrome tabs to crash?
Yes, I got it now.
From https://github.com/mozilla/pdf.js/issues/4104, I found the answer (thanks Rob and PDF.js dev team!). Take a look yourself!
I'm only posting this here so that anyone who stumbles upon this post with a similar problem can be helped (as this error took me quite a while to figure out).
Unfortunately, this does not seem to be the case. We've tried the latest version of pdf.js from github, also tried Chrome 33 (stable) which should have their V8 fix included and it still crashes. Also, tried the pdf.js commit mentioned in github thread (4ce6cb8 - https://github.com/mozilla/pdf.js/commit/4ce6cb8b0fa9db948516b2b738fa1503cf0ef90e) - still crashes. Also tried latest Chrome Canary available on 19/03/2014 - crash is there.
We can provide the WinDbg memory dump if it's of any help.
PS: sorry, this should be the answer to Rob W thread right above but I cannot add it there due to 0 reputation.
My problem may seem a bit vague (it is to me too), but here is my attempted explanation of it.
A few months ago, I implemented PDF.js in my web application. It was really useful, and I am using it for interactions with my clients.
Suddenly, last week, my clients reported to me "Aw, Snap" messages in Google Chrome on their PCs when they try to launch PDF.js. I have an iMac and two PCs at home, so I decided to test this out.
When I used Google Chrome on my iMac to launch PDF.js, I found it worked fine.
When I used Google Chrome on my first PC to launch PDF.js, I found it worked fine.
When I used Google Chrome on my second PC to launch PDF.js, even though it previously worked, it kept crashing and showing me "Aw, Snap" messages.
This was weird. I tried removing all the extensions, clearing the cache, clearing the LocalStorage, but nothing seemed to fix the problem.
I then realised, after some communication with my clients, launching PDF.js in Safari, Torch, Opera or Firefox on any operating system worked perfectly fine.
Why would this happen? I am using the web viewer in PDF.js. I also tried with the basic hello world example, but that broke as well (which I now find really weird), so I suspect there's something wrong with the rendering engine.
I also tried including the compatibility.js file after building the source, but with no avail.
Is there any known bug which causes Google Chrome tabs to crash?
Yes, I got it now.
From https://github.com/mozilla/pdf.js/issues/4104, I found the answer (thanks Rob and PDF.js dev team!). Take a look yourself!
I'm only posting this here so that anyone who stumbles upon this post with a similar problem can be helped (as this error took me quite a while to figure out).
Unfortunately, this does not seem to be the case. We've tried the latest version of pdf.js from github, also tried Chrome 33 (stable) which should have their V8 fix included and it still crashes. Also, tried the pdf.js commit mentioned in github thread (4ce6cb8 - https://github.com/mozilla/pdf.js/commit/4ce6cb8b0fa9db948516b2b738fa1503cf0ef90e) - still crashes. Also tried latest Chrome Canary available on 19/03/2014 - crash is there.
We can provide the WinDbg memory dump if it's of any help.
PS: sorry, this should be the answer to Rob W thread right above but I cannot add it there due to 0 reputation.
Our about and preferences flyouts, which worked under RC, are now blank/white after converting the project to RTM. We had used example code from the win8 labs to construct these and they were working before. I have read the migration guide and have made changes that seemed applicable. Is anyone else experiencing this problem, and is there a solution for this? We are using Javascript. Thanks.
With the RTM release there are a lot of breaking changes, so you should take a look to the migration provided by Microsoft migration guide
If you have used z-index, you must know that z-index range changed from 1000-1003 to 1000-1008
Regards.
I downloaded the latest jQuery UI from their Themeroller site wanting to implement ui-checkboxes and cannot "seem" to find any reference or examples for it any longer.
Here is an online example of what I was hoping to implement
This is all I have found to be available (...and I hate this)
Did it go away?
And if so, why?
The version is I downloaded was jquery-ui-1.8.16 (I downloaded the entire thing). I searched all the CSS files with no mention of the tag ui-checkbox.
...it just struck me as odd.
According to that I have found, that particular plugin was broken past the 1.7.2 version of jquery, so it is broken. However, someone did make a version (not sure how compatible it is with the newest versions) that is compatible with 1.8.5. That can be found here
I don't think it's part of the official jquery-ui package. Is it this plugin?