Closed Bug 8806 Opened 25 years ago Closed 25 years ago

Print not working

Categories

(Core :: Printing: Output, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sujay, Assigned: cmanske)

References

Details

using 6/23 build of apprunner on all platforms

1) launch apprunner
2) launch editor
3) click on Print button

nothing happens. no print dialog comes up.
Assignee: buster → cmanske
assigned to charlie.  this should be very easy.  direct questions about printing
to don cone.
Status: NEW → ASSIGNED
Target Milestone: M8
Target Milestone: M8 → M9
This is more difficult than I originally thought. The browser implements this
in JS, but it is still using appcores and I don't know how to get ahold of the
appropriate appcore name so I can do the same thing they do. It may be simpler
to wait until they convert the browser to the XPIDL version of the browser UI
interface.
also, we'll have a little more work to do since we'll need to save this into a
temporary file (if it hasn't been saved or has unsaved changes).
I don't think the temp file stuff is necessary in Gecko world. I believe they
just render the current tree to a print context instead of having to fetch the
contents from the net like in 4.x. Isn't that COOL!
Target Milestone: M9 → M11
This should be easier to solve by using the new XUL overlay method of merging
menus. The Print item should be merged from global.xul so it is handled by
the same code as in the browser.
*** Bug 10663 has been marked as a duplicate of this bug. ***
adding cc from duplicate bug (#10663)
Blocks: 11275
> I believe they just render the current tree to a print context...

If I understand what you're saying, that's incredibly cool. Are you basically
saying that instead of rendering the document tree to the on-screen browser
window context, you render it to the context of a print document? Are you saying
the rendering engine renders to an abstract "context" interface? This has a lot
of implications -- is it the same with the browser? Anyway, if that's what
you're saying, I will forever chant "I'm not worthy, I'm not worthy"...
My intention was to do exactly what the Browser does, which should make this
a snap, but the last time I looked the browser was still accessing core
print command via their "appcore". I don't know how to get ahold of a browser
appcore from the editor. I was hoping the Browser would abandon the appcore
eventually, but it still seems to use it.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Checked in 9/14
Status: RESOLVED → REOPENED
I grabbed the 9/15 build and I don't see it working....it should
have been in 9/15 build if you checked in 9/14...
Are you sure a build on a particular day isn't really the final version from
the day before? What time are the builds you get ready? If I check in on day
"x", it won't be varified until around noon the next day, so if you are
picking up a build in the morning, it is too early.
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen.
Charley this is still not working in 9/17 build...
Status: REOPENED → ASSIGNED
Ok, so I wasn't paying close enough attention to how to produce this.
Printing does work from the menu (File | Print) but the toolbar button isn't
connected correctly
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Checked in 9/17/99
Status: RESOLVED → VERIFIED
verified in 9/21 build.
Status: VERIFIED → REOPENED
Reopening. Nothing prints out of the 11/19 build.
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
the checkin was after 1:00pm today, so I suspect you haven't got it in the build
your testing.  marking fixed again, please verify against an afteroon build or
the next daily build.

also, I think you marked the wrong bug reopeend.  this is an
editor-specific bug about print not being enabled yet.  I think you meant 19381

thanks!
Component: Editor → Printing
QA Contact: sujay → shrir
shrir, please verify.
Status: RESOLVED → VERIFIED
verified using 11/24 commercial build
You need to log in before you can comment on or make changes to this bug.