Text wrap setting in Table Cell Properties may be ignored.

RESOLVED EXPIRED

Status

SeaMonkey
Composer
RESOLVED EXPIRED
15 years ago
8 years ago

People

(Reporter: Mark Lassau, Assigned: glazou)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208

When you set the "Text-Wrap" property of a table cell to Wrap, Composer removes
the CSS "white-space" property rather than explicitly setting it to white-space:
normal;
This means the cell will just take on the default setting which could be
something other than normal.

Reproducible: Always

Steps to Reproduce:
1. Create a new table and accept the default values.
2. Add text to one of the cells until it wraps the text.
3. Change to Source view and set the <tbody> tag to "nowrap"
     <tbody style="white-space: nowrap;">
4. Change back to Normal view (text doesn't wrap now)
5. Open the Table Cell Properties dialog for the cell in question 
    (Table | Table Properties)
6. Change text-align to Wrap and click OK.

Actual Results:  
The cell's text did not wrap.

Expected Results:  
The cell's text should now wrap.

This was originally reported in bug 230165, but has been split into smaller chunks.

I have "Use CSS styles instead of HTML elements and attributes" checked in
Preferences/Composer (this is the default setting).

To fix this I suggest an extra option in the Text-Wrap drop-down.
It would have a display value of "", or "default" or some such.
It would remove the style property.
The "Wrap" option would add an explicit CSS property of "white-space: normal;"

Note that CSS defines a third white-space value of "pre", which works like the
<pre> HTML tag.
It would be nice enhancement to include this in the drop-down, although it has
no equivalent in the deprecated HTML attributes that Mozilla Composer still
supports.
(Assignee)

Comment 1

15 years ago
taking
Assignee: composer → daniel
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Browser → Seamonkey

Comment 2

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

Comment 3

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.