105536 - RFE: new schema/page layout

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[sujay]

Would be great if we could have a page layout view so when I'm writing a
document, I know how many pages it is as an offline/printed document- don't know
what this looks like maybe an 8.5"x11" page consists of x amount of lines and we
display a page break after x amount of lines.  If they change page layout
preferences, landscape view, we know the page break will then display after y
amount of lines.

Comment 1

[sujay]

bulk move to Future...sorry for the spam

Comment 2

[Charles Manske]

HTML editors are not oriented toward printing. We don't even have Print Preview
yet! There's very little chance that this could be implemented.

Comment 3

[Rafael Ebron (:rebron)]

Requires CSS 2 implementation paged media. Not supported in the browser yet.
http://www.w3.org/TR/REC-CSS2/page.html

And hopefully print preview is coming to composer.

HTML editors should be oriented towards printing.  All the documents I write for
work are through composer and I print as well as post these documents online.  I
would love to be able to control my page breaks via composer so when a user
prints my page from the browser, it's printed as I have controled it to be printed.

Printing HTML, whether it's through the browser or composer should not suck. 
Need to be able to allow authors and viewers to control printing.  This bug is
to give authors control.  

Comment 4

[Kathleen :Brade]

reassign to new placeholder

Comment 5

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420