Created attachment 8433030
Fix size for gfxQuartzSurface
Oh man, this bug just doesn't end. Unfortunately yesterday was a public
holiday, so only just got to this now.
I've confirmed that this patch fixes printing for OSX. Building on linux
now.
--
You received this bug notification because
And confirmed that it also fixes the issue for ubuntu.
https://hg.mozilla.org/integration/mozilla-inbound/rev/817ede736aa
Lukas, this is a very low risk continuation of the previous fix, we
should uplift it to beta if it's not too late.
--
You received this bug notification because you are a
https://hg.mozilla.org/integration/mozilla-inbound/rev/809f9bcbd7f2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1315020
Title:
PDF.js prints blank pages
Status in The Mozilla
Created attachment 8426804
Implement size for recording surface created for windows printing
Ok, confirmed that it's still broken on beta.
It appears that for windows printing we create a gfxWindowsSurface that
is backed by a cairo recording surface. So when we call
CreateSimilarSurface, we end
(In reply to Lukas Blakk [:lsblakk] from comment #69)
Matt - what's missing for this on Beta? Have you got a follow up fix coming
here for branches?
It should have been fixed on beta, the patch has been uplifted.
--
You received this bug notification because you are a member of Desktop
Created attachment 8421451
Beta branch patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1315020
Title:
PDF.js prints blank pages
Status in The Mozilla Firefox Browser:
Fix
Comment on attachment 8417932
Pass surface sizes in
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 991767
User impact if declined: Broken printing
Testing completed (on m-c, etc.): Been on m-c for a week or so.
Risk to taking this patch (and alternatives if risky):
It's
(In reply to Vladimir G. Ivanovic from comment #45)
I am using the Arch package firefox-29.0.1-1 (built 2014-05-09T12:31:49 PDT)
and the bug is still present, so I don't understand why it's been marked
RESOLVED FIXED.
We mark bugs as resolved once they are fixed on mozilla-cental (firefox
32
(In reply to Henrik Skupin (:whimboo) from comment #38)
Can this be tested by an automated test?
I don't think so.
The bug was specific to GDI printing surfaces, which we can't use in any
of our existing test suites.
We'd need a new suite/harness that actually prints (probably to a
virtual
https://hg.mozilla.org/integration/mozilla-inbound/rev/3b5fb4abaa3f
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1315020
Title:
PDF.js prints blank pages
Status in The Mozilla
Created attachment 8417932
Pass surface sizes in
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1315020
Title:
PDF.js prints blank pages
Status in The Mozilla Firefox Browser:
This bug refers to an issue that could only occur *without* hardware
acceleration.
Hardware acceleration is currently incomplete on linux, and is disabled
by default for all users.
You're probably seeing bug 777170, which is because the component alpha
(sub-pixel alpha text) support isn't
12 matches
Mail list logo
