4 ms·
Reporting bugs in Firefox is intimidating to say the least. Will a bug filed at GitHub like https://github.com/mozilla/pdf.js/issues/4761 https://github.com/moz
by voltagex_ 13y ago
Reporting bugs in Firefox is intimidating to say the least. Will a bug filed at GitHub like https://github.com/mozilla/pdf.js/issues/4761 https://github.com/mozilla/pdf.js/issues/4761 still reach the right place?
bgirard's profiling work in this thread has been amazing, but I don't think I have the knowledge to interpret the profiler results well enough to file bugs on slow PDFs. A way to post "slow" PDFs to be picked up by pdf.js developers would help.
- nnethercote 13y ago> Will a bug filed at GitHub like https://github.com/mozilla/pdf.js/issues/4761 https://github.com/mozilla/pdf.js/issues/4761 still reach the right place? Filing at Bugzilla will probably give you a wider audience. This can be useful if the underlying perf problem is with Firefox rather than pdf.js. Don't worry about getting some of the Bugzilla fields wrong, it happens all the time and people don't mind. A good description of the problem (with steps to reproduce) is the most important thing. If you're still intimidated, filing something with pdf.js's GitHub tracker is a lot better than nothing.
- async5 13y agoFiling nothing will not be helpful for sure. Creating a report in any related bug reporting system will bring developer's, QA's or manager's attention. Just provide enough information, so somebody else except you can reproduce the problem.