Closed
Bug 144128
Opened 23 years ago
Closed 23 years ago
[FIX]API Freeze - Need to create PrintSettings w/o nsIWebBrowserPrint
Categories
(Core :: Printing: Output, defect)
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: rods, Assigned: rods)
References
Details
(Keywords: topembed+, Whiteboard: [adt2])
Attachments
(3 files)
58.16 KB,
patch
|
dcone
:
review+
attinasi
:
superreview+
|
Details | Diff | Splinter Review |
2.82 KB,
patch
|
Details | Diff | Splinter Review | |
2.58 KB,
patch
|
dcone
:
review+
kinmoz
:
superreview+
|
Details | Diff | Splinter Review |
There needs to be a service for creating the nsIPrintSettings objects and then
remove them from nsIWebBrowserPrint.
Because there times when you will need to get a PrintSettings object and you do
not have a nsIWebBrowserPrint object.
The new service "nsIPrintSettingsService" will be implemented by nsPrintOptions
and I have already filed a bug 144114 for switch over the impl's name.
For now, nsIPrintOptions and nsIPrintSettingsService will have the same CID
because the same object implements both services. NOTE: only internal classes
will ever need to create a nsIPrintOptions object.
Assignee | ||
Updated•23 years ago
|
Assignee | ||
Comment 1•23 years ago
|
||
Problem: You cannot create a PrintSettings object without a nsIWebBrowserPrint
iface which requires a loaded document.
Solution: Move the creation and manipulation of PSs to their own service.
This patch does the following:
1) Introduces a new public interface nsIPrintSettingService which emables
consumers to create PS objects whithout a nsIWebBrowserPrint interface
2) The implementation is nsPrintOptionsImpl which now impls the private
interface nsIPrintOptions and the public iface nsIPrintSettingsService
3) Several methods/attrs have been moved from nsIWebBrowserPrint iface to
nsIPrintSettingsService
4) The CIDs for nsIPrintOptions and nsIPrinSettingsService are now the same.
5) There is no longer a CID "@mozilla.org/gfx/printoptions;1"
6) nsIWebBrowserPrint still has the "globalPrintSettings" attr so if you
already have an nsIWebBrowserPrint you don't have to create the PS Service to
get it.
7) A bug has been filed to rename the imlp of nsPrintOptionsImpl to
nsPrintSettingsService.
Assignee | ||
Updated•23 years ago
|
Summary: API Freeze - Need to create PrintSettings w/o nsIWebBrowserPrint → [FIX]API Freeze - Need to create PrintSettings w/o nsIWebBrowserPrint
Comment 2•23 years ago
|
||
Comment on attachment 83351 [details] [diff] [review]
patch
sr=attinasi, assuming you document the transitional nature as we discussed on
the phone.
Attachment #83351 -
Flags: superreview+
Assignee | ||
Comment 4•23 years ago
|
||
Assignee | ||
Comment 5•23 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Keywords: adt1.0.0
Resolution: --- → FIXED
Whiteboard: [adt2]
Comment 6•23 years ago
|
||
Comment on attachment 83351 [details] [diff] [review]
patch
r=dcone
Attachment #83351 -
Flags: review+
printing and page setup work in 5/15 build.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 8•23 years ago
|
||
Reopening, I messed a directory when making the patch and checking in
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•23 years ago
|
||
I missed this dir for patch and checkin
Assignee | ||
Updated•23 years ago
|
Status: REOPENED → ASSIGNED
Comment 10•23 years ago
|
||
Comment on attachment 83920 [details] [diff] [review]
mailnews part of patch
r=dcone
Attachment #83920 -
Flags: review+
Comment 11•23 years ago
|
||
Attachment #83920 -
Flags: superreview+
Assignee | ||
Comment 12•23 years ago
|
||
ducarroz says dcone's r= is fine - fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Comment 13•23 years ago
|
||
Rod, can you verify this and mark verified-fixed? thanks.
Comment 14•23 years ago
|
||
adding adt1.0.0+. Please get drivers approval and then check into the 1.0 branch.
Comment 16•23 years ago
|
||
changing to adt1.0.1+ for checkin to the 1.0 branch for the Mozilla1.0.1
milestone. Please get drivers approval before checking in.
Comment 17•23 years ago
|
||
please land on the 1.0.1 branch. once there, remove the "mozilla1.0.1+" keyword,
and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1+
Keywords: fixed1.0.1 → verified1.0.1
You need to log in
before you can comment on or make changes to this bug.
Description
•