Form elements not rendered correctly when right-click+reload

NEW

Status

()

Core
HTML: Form Submission
P4
minor
15 years ago
8 years ago

People

(Reporter: Franz Graf, Assigned: John Keiser (jkeiser))

Tracking

Trunk
Future
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020614
BuildID:    2002061408

Radiobuttons ar not rendered correctly when editing their status (checked
/unchecked) and reload via right-klick -> reload

Reproducible: Always
Steps to Reproduce:
1. create a simple form with an unchecked radiobutton (<input type="radio">) and
an unchecked checkbox
2. view it in Mozilla
3. edit both to checked (<input type="radio" checked>) - keep Mozilla open
during this
4. right-click : reload (or click on browserbutton "reload")


Actual Results:  The radiobutton remains unchecked although right-click + view
source shows "checked" in the source.
The checkbox shows up checked as expected.

Expected Results:  Radiobutton should show up checked OR the checkbox unchecked.
At least both should behave the same way.

It's no problem at all if the Form is a frameless page as you can easily hit
STRG+Shift+Reload.
It just su*** a bit if the form is nested in a frame. You then have to reenter
this page through a link or reload the complete frameset which might not be wanted.

I'm not really sure if it is a dupe of bug 46845 (
http://bugzilla.mozilla.org/show_bug.cgi?id=46845 )

Comment 1

15 years ago
to john
Assignee: alexsavulov → jkeiser
This basically looks like a dup of bug 46845 modulo bugs in form state
restoration....
Depends on: 46845

Comment 3

15 years ago
Confirming for now, but I'm pretty sure I've seen exact dupe. Bug 44008 also
seems related.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4
Bulk moving P1-P5 un-milestoned bugs to future. 
Target Milestone: --- → Future
QA Contact: vladimire → form-submission
You need to log in before you can comment on or make changes to this bug.