Closed
Bug 8806
Opened 26 years ago
Closed 25 years ago
Print not working
Categories
(Core :: Printing: Output, defect, P3)
Core
Printing: Output
Tracking
()
VERIFIED
FIXED
M11
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.
assigned to charlie. this should be very easy. direct questions about printing
to don cone.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M8
Assignee | ||
Updated•26 years ago
|
Target Milestone: M8 → M9
Assignee | ||
Comment 2•26 years ago
|
||
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.
Comment 3•26 years ago
|
||
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).
Assignee | ||
Comment 4•26 years ago
|
||
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!
Assignee | ||
Updated•26 years ago
|
Target Milestone: M9 → M11
Assignee | ||
Comment 5•26 years ago
|
||
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.
Comment 7•26 years ago
|
||
adding cc from duplicate bug (#10663)
> 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"...
Assignee | ||
Comment 9•25 years ago
|
||
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.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•25 years ago
|
||
Checked in 9/14
Reporter | ||
Comment 11•25 years ago
|
||
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...
Assignee | ||
Comment 12•25 years ago
|
||
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.
Comment 13•25 years ago
|
||
Clearing FIXED resolution due to reopen.
Reporter | ||
Comment 14•25 years ago
|
||
Charley this is still not working in 9/17 build...
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 15•25 years ago
|
||
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
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 16•25 years ago
|
||
Checked in 9/17/99
Reporter | ||
Comment 17•25 years ago
|
||
verified in 9/21 build.
Updated•25 years ago
|
Status: VERIFIED → REOPENED
Comment 18•25 years ago
|
||
Reopening. Nothing prints out of the 11/19 build.
Comment 19•25 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!
Comment 20•25 years ago
|
||
shrir, please verify.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 21•25 years ago
|
||
verified using 11/24 commercial build
You need to log in
before you can comment on or make changes to this bug.
Description
•