If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

RFE: Unable to enter content adjacent to a table

RESOLVED EXPIRED

Status

SeaMonkey
Composer
--
enhancement
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: TucsonTester1, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4)
Gecko/20011019 Netscape6/6.2
BuildID:    20011022

Only able to enter content (text, image, link, etc) above a table, in a table,
or below a table.  Being able to enter content to the left of a table, or to the
right of a table would seem to me to be a desirable thing.

Reproducible: Always
Steps to Reproduce:
1.Open a blank page in composer
2.Click on table
3.Change width to 30 (% of window) and click ok
4.Attempt to enter text outside of table so it appears beside the table

Actual Results:  Only able to enter text above the table, below the table or in
the table.

Expected Results:  I would like to be able to use the space next to the table
for text, images or other content, instead of having to leave it blank.

I assume this to be an enhancement and not a bug.  I know it is possible to do
in some web authoring tools, since I have seen pages designed this way.  But I
have been unable to find a way to do this in composer.

Updated

16 years ago
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: Unable to enter content adjacent to a table → RFE: Unable to enter content adjacent to a table
Target Milestone: --- → Future

Comment 1

15 years ago
reassign to new account
Assignee: syd → composer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: composer → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---

Comment 2

8 years ago
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

Comment 3

8 years ago
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
Group: core-security

Comment 4

8 years ago
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

Updated

8 years ago
Group: core-security

Comment 5

8 years ago
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
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.