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

shading-filled bars in figure 10 of tracemonkey paper don't render on some OS's in firefox #15

Closed
joneschrisg opened this issue Jun 16, 2011 · 8 comments

Comments

@joneschrisg
Copy link
Contributor

On X11, android, and windows XP systems, the bars will likely not render. This is because of https://bugzilla.mozilla.org/show_bug.cgi?id=664077 . Filing this issue to track the Mozilla bug.

@notmasteryet
Copy link
Contributor

@brendandahl, you were looking for this issue

@qqqqqq
Copy link

qqqqqq commented Sep 17, 2012

using skia azure backend fixes the issue on win xp (gfx.canvas.azure.backends = direct2d,skia,cairo)

@timvandermeij
Copy link
Contributor

I can confirm that the shading bars in figure 10 do not render on Android 4.3 with Firefox 23.0.1 and the latest PDF.js development version.

@yurydelendik
Copy link
Contributor

@SamyCookie
Copy link

I do not see this bug anymore on my machines with the demo tracemonkey paper.

  • Debian Stretch (testing) 64 bits, firefox 39b1 and "PDF 110dd61fd57444010b1ab5ff38782f0f [1.4 pdfeTeX-1.21a / TeX](PDF.js: 1.1.185)"
  • Debian Jessie (stable) 64bits, Firefox 38.0.1, and "PDF 110dd61fd57444010b1ab5ff38782f0f [1.4 pdfeTeX-1.21a / TeX](PDF.js: 1.1.185)"

However, the upstream bug is not marked as fixed.
Anyone else can confirm that ?

@SamyCookie
Copy link

@timvandermeij Could you test this one too ? I think it's fixed now.

@timvandermeij
Copy link
Contributor

I can reproduce this issue on Arch Linux x64. The canvas backend I use is Cairo.

@timvandermeij
Copy link
Contributor

timvandermeij commented May 1, 2016

I have confirmed that Firefox 48 fixes this for me on Arch Linux. Closing as fixed, but if someone encounters this issue again after Firefox 48, please create a new issue with all details about the browser and OS.

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

6 participants