36147 - Some DOM1 align attributes for INPUT are not being set correctly

Status: RESOLVED INVALID

(Core :: DOM: Core & HTML, defect, P3)

Description

[Jan Carpenter]

Overview Description: 
The align attribute has the following definition:
align = bottom|middle|top|left|right

Setting align=bottom sets .align to "baseline"
Setting align=middle sets .align to "center"
Leaving align unset should result in .align set to "bottom", however it is 
currently not set to anything.

Setting align=center sets .align to "center" even though "center" should not be 
an option.  I'm not sure what it should be set to, maybe "bottom" as that is the 
default.

Steps to Reproduce: 
- see attached testcase

Actual Results: 
align=bottom sets .align to "baseline"
align=middle sets .align to "center"
Leaving align unset doesn't set .align to anything

Expected Results: 
align=bottom sets .align is set to "bottom"
align=middle sets .align is set to "middle"
Leaving align unset .align is set to "bottom" 
(The spec says the default is "bottom" so I am assuming that it should be set to 
this initially.)

Build Date & Platform Bug Found: 
2000-04-17-06-M15 Win98

Additional Builds and Platforms Tested On: 
2000-04-17-06-M15 Mac
2000-04-17-06-M15 WinNT
(Linux build not working now, will check later)

Comment 1

[Jan Carpenter]

Attachment: attaching testcase

Comment 2

[Jan Carpenter]

changing qa contact

Comment 3

[Jan Carpenter]

nominating for nsbeta2

Comment 4

[Phil Peterson]

[nsbeta2+]

Comment 5

[Johnny Stenback (:jst)]

Why is this beta2, this is IMO nowhere close to a beta2 blocker?

Comment 6

[Jan Carpenter]

This was nominated for nsbeta2 because "align" is a high profile attribute that 
doesn't work per the spec for several elements.

Comment 7

[Johnny Stenback (:jst)]

Handing this one over to Vidur.

Comment 8

[vidur (gone)]

The issue is not that they aren't being set correctly (they are handled 
correctly by layout), but that we are losing some information during the 
reverse mapping from the stored values to strings. We are not breaking 
compatibility with 4.x and existing scripts since this attribute wasn't part of 
DOM Level 0. I really believe that this is not nsbeta2 crucial and can even be 
Futured. 

I'm going to remove nsbeta2+ from the status whiteboard so that it can be 
reconsidered. I'd recommend making it a nsbeta2-.

Comment 9

[Jay Patel [:jay]]

Putting on [nsbeta2-] radar. Not critical to beta2. 

Comment 10

[Johnny Stenback (:jst)]

This bug has been marked "future" because the original netscape engineer
working on this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work
in some way -- please attach your concern to the bug for reconsideration.

Comment 11

[Prashant Desale]

QA contact Update

Comment 12

[vidur (gone)]

Normalizing obsolete or non-standard attribute values to their current standard 
equivalent as we are doing seems like a valid thing to do. Marking this bug 
INVALID.

Comment 13

[Prashant Desale]

Updating QA contact to Shivakiran Tummala.

Comment 14

[Sivakiran Tummala]

still see the same problem ...
Setting align=bottom sets .align to "baseline"

Comment 15

[Fabian Guisset]

sivakiran, could you explain why you reopened this? Vidur said
"Normalizing obsolete or non-standard attribute values to their current standard 
equivalent as we are doing seems like a valid thing to do."
This means that bottom becoming baseline is "expected".

Comment 16

[Boris Zbarsky [:bzbarsky]]

Re-marking invalid.