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

Rendering problem of border-radius in Adobe Reader #360

Closed
inuyasha2012 opened this Issue Sep 22, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@inuyasha2012

inuyasha2012 commented Sep 22, 2016

when I use border-radius, I find a problem

in browser, like firefox, IE, it rendered right

but in adobe reader, it rendered some strange thin lines

i don't kow why, the pic is below

p

@liZe liZe changed the title from the render problem of border-radius in adobe reader to Rendering problem of border-radius in Adobe Reader Sep 22, 2016

@liZe liZe added the bug label Sep 22, 2016

@liZe

This comment has been minimized.

Show comment
Hide comment
@liZe

liZe Sep 22, 2016

Member

Thanks for reporting!

I've tried to reproduce, and some readers seem to have this problem:

  • Adobe Reader
  • ImageMagick
  • Ghostscript

Some other don't:

  • Evince
  • Foxit
  • Firefox
  • Chrome
  • Edge

As this problem is not visible in all readers and not visible in PNGs generated by Cairo, I suppose that there's a bug in either these readers and/or in Cairo, and a "strange" use of the drawing primitives of Cairo in WeasyPrint. We can try to find and change this "strange" use to fix the problem.

Member

liZe commented Sep 22, 2016

Thanks for reporting!

I've tried to reproduce, and some readers seem to have this problem:

  • Adobe Reader
  • ImageMagick
  • Ghostscript

Some other don't:

  • Evince
  • Foxit
  • Firefox
  • Chrome
  • Edge

As this problem is not visible in all readers and not visible in PNGs generated by Cairo, I suppose that there's a bug in either these readers and/or in Cairo, and a "strange" use of the drawing primitives of Cairo in WeasyPrint. We can try to find and change this "strange" use to fix the problem.

@liZe liZe closed this in 526bbd2 Oct 24, 2017

@liZe liZe added this to the v0.42 milestone Oct 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment