Closed Bug 203875 Opened 22 years ago Closed 9 months ago

Composer changes MultiLengths of "*" to "1*"

Categories

(Core :: DOM: Serializers, defect, P5)

x86
Windows 98
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: ernestcline, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 While these are supposed to be the same, the simple fact is that IE can handle "*" and can't handle "1*". Not only that, but "*" is shorter. If anything, composer should be changing "1*" MultiLengths to "*", not the other way around, even if IE did not have that bug. Reproducible: Always Steps to Reproduce: 1. Enter any HTML code with a MultiLength of "*" for a width value used in it. Actual Results: Composer changes it to "1*". Expected Results: Leave it alone.
-->DOM to Text Conversion
Assignee: composer → harishd
Component: Editor: Composer → DOM to Text Conversion
QA Contact: petersen → sujay
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
I still get this bug in Composer. If one enters <col width="*"> as source it converts it into <col width="1*"> which while theoretically equivalent according to the standards, isn't, as mentioned in my initial bug report.
Assignee: harishd → nobody
QA Contact: sujay → dom-to-text

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

Hmm, I didn't know the special width value... It's not in current HTML Standard anymore, but it was defined by HTML 4.01:

Proportional specifications (e.g., width="3*") refer to portions of the horizontal space required by a table. If the table width is given a fixed value via the width attribute of the TABLE element, user agents may render the table incrementally even with proportional columns.

However, if the table does not have a fixed width, user agents must receive all table data before they can determine the horizontal space required by the table. Only then may this space be allotted to proportional columns.
<snip>
Once the (visual) user agent has received the table's data: the available horizontal space will be alloted by the user agent as follows: First the user agent will allot 30 pixels to columns one and two. Then, the minimal space required for the third column will be reserved. The remaining horizontal space will be divided into six equal portions (since 2* + 1* + 3* = 6 portions). Column four (2*) will receive two of these portions, column five (1*) will receive one, and column six (3*) will receive three.

<TABLE>
<COLGROUP>
   <COL width="30">
<COLGROUP>
   <COL width="30">
   <COL width="0*">
   <COL width="2*">
<COLGROUP align="center">
   <COL width="1*">
   <COL width="3*" align="char" char=":">
<THEAD>
<TR><TD> ...
...rows...
</TABLE>

Okay, so, 1* should be reasonable even in the old spec. Although I don't know this is handled by current layout module, the editor module does not need to save only one byte with the invalid form.

Status: UNCONFIRMED → RESOLVED
Closed: 9 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.