125597 - [0.9.4 branch] 'readonly' attribute of INPUT not working

Status: RESOLVED WORKSFORME

(Core :: Layout: Form Controls, defect)

Description

[Christine Hoffman]

Testing on the following:

Mfcembed 02_05_22_0.9.4ec
Netscape trunk 02_12_02_trunk

Open the attached HTML and XHTML testcases.

The INPUT element has a 'readonly' attribute for 'text' and 'password'.

Expected behavior: The 'readonly' attribute should prohibit changes  to the control
Actual behavior: Works in a current trunk build but it is a REGRESSION in the
0.9.4ec Mfcembed branch build
Regression applies to HTML and XHTML.

Comment 1

[Christine Hoffman]

Worked in 6.2

Comment 2

[Christine Hoffman]

Attachment: HTML-password_readonnly

Comment 3

[Christine Hoffman]

Attachment: HTML-text_only

Comment 4

[Christine Hoffman]

Attachment: XHTML-password_readonly

Comment 5

[Christine Hoffman]

Attachment: XHTML-text_readonly

Comment 6

[Christine Hoffman]

This happens with textarea_readonly as well.

Comment 7

[Christine Hoffman]

Nominating for EDT to keep on compass - regression on branch

Comment 8

[rods (gone)]

I think this is a dup? 

All these tests work for me in today's build with win2k. I you need to re-open
assign to kin.

Comment 9

[Michael Dunn]

Minusing for 094. Comment as appropriate.

Comment 10

[Christine Hoffman]

Tested on 04_03_16_trunk mfcembed build. Still seeing this problem. Reopening bug

Comment 11

[rods (gone)]

-->

Comment 12

[Christine Hoffman]

Changing QA contact

Comment 13

[Ron Cemer]

This is serious.  It's allowing people to change the conents of readonly input
elements on the form, which is unacceptable.  A common practice is to use
readonly fields to show data that is collected from other user actions.  If the
user can then edit that field that is supposed to be readonly, then the screen's
display is now out of sync with the collected data.  If the readonly field is
looked at by the server, it can be a security issue because the user can just
put anything into that field.

Please change the severity of this bug to critical and see if we can get it
fixed ASAP.

I'm using 1.1 alpha (1.1 beta crashes too often for me).

Comment 14

[Kathleen :Brade]

I am resolving this as "worksforme" since I am unable to reproduce the problem
on my mozilla debug build (trunk) from 2 days ago.