Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashed line rendered solid in Chromium #6143

Closed
pcworld opened this issue Jun 25, 2015 · 6 comments
Closed

Dashed line rendered solid in Chromium #6143

pcworld opened this issue Jun 25, 2015 · 6 comments

Comments

@pcworld
Copy link

pcworld commented Jun 25, 2015

Page 2 of this PDF contains dashed lines, which are rendered solid in Chromium 43 using this this online demo of pdf.js, but fine in Firefox 38.0.

How it is rendered in Chromium:
selection_268
Same page in Evince:
selection_269

According to #1012, a similar issue was going to be fixed with #2429, however I'm not sure if this is the same issue here.

@Rob--W
Copy link
Member

Rob--W commented Jun 30, 2015

I reduced the test case using the technique that I documented at #5043 (comment).

This is a recent bug in Chromium (since version 43):
https://code.google.com/p/chromium/issues/detail?id=505912

@pcworld
Copy link
Author

pcworld commented Jun 30, 2015

This is a recent bug in Chromium (since version 43)

The linked bug affects versions starting from at least 34. It was marked as a duplicate of a bug that is from July 2013.
So shouldn't either earlier Chromium versions be affected as well (I haven't tried) or is this a different bug?

@Rob--W
Copy link
Member

Rob--W commented Jun 30, 2015

@pcworld The bug from my previous comment was filed 25 minutes ago by me. I only referred to the other bug at PDF.js to explain how I created the reduced test case (in case you want to create one yourself, in the future).

@pcworld
Copy link
Author

pcworld commented Jun 30, 2015

@Rob--W Sorry, I mixed up the issue tracker links then.

@timvandermeij
Copy link
Contributor

@Rob--W This seems to have been fixed upstream. Could you verify this and close the issue if it is indeed fixed?

@Rob--W
Copy link
Member

Rob--W commented Jul 12, 2015

@timvandermeij This has indeed been fixed upstream and merged back to 44, but not 43. I've verified that the bug has been fixed in 46.0.2455.0 (and therefore also in 45 and 44).

Within a few weeks, Chrome will upgrade to 44. Since there's nothing that we (as PDF.js devs) can do to fix this issue in 43 (except for patching the .save/.restore methods), I'll close the bug.

@Rob--W Rob--W closed this as completed Jul 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants