Closed Bug 169960 Opened 23 years ago Closed 16 years ago

RFE: ability to separate a big table on sections

Categories

(SeaMonkey :: Composer, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: olgam, Unassigned)

Details

Ability to divide long table on parts will make editing Composer features even more flexible. I believe, it will help to work on new or restructure existing different documents. In Word I inserted Page Break in the middle of a table. Then pasted a Header, removed page break, and had a new separate part of a table. Current Composer functionality allows to insert or remove rows, copy/page either complete table or just one cell. (Or just a part of it.) If we could divide a big table for sections, we won't need to do major copy/paste, just reuse existing parts, probably remove repetitive text when combine some parts in sections. In case of testing documents, our test cases combined in proper sections, will provide more consice test plan - since we can remove repetitive text. It will decrease time for running them. Also test plan with clear logic and test objective emphasised with the name of separate sections, increases creativity for new test cases. So, hopefully we will move from better documents to even better product.
Status: NEW → ASSIGNED
reassign to new account
Assignee: syd → composer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
MASS-CHANGE: 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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.