Open Bug 111486 Opened 23 years ago Updated 2 years ago

xul:textbox.value doesn't persist (because value attribute isn't always equal to the value property)

Categories

(Core :: XUL, defect)

defect

Tracking

()

People

(Reporter: axel, Unassigned)

Details

Attachments

(1 file)

654 bytes, application/vnd.mozilla.xul+xml
Details
Using persist for a textbox doesn't write back the value of the textbox anymore.
It does however use an existing value from localstore.
Adding jkeiser, as I suspect his forms rewrite to regress this.
A small xulet is coming up.
Attached file textbox-persist.xul
I was so proud that I found the mimetype, and now there's just a select option
for it. My day is spoiled. :-) (hrm. we have xul, but not xml. nice)

This testcase has a textbox with id 'fld', I'll post a snippet for 
localstore.rdf once I know the url.
adding
  <RDF:Description
about="http://bugzilla.mozilla.org/attachment.cgi?id=58879&amp;action=view">
    <NC:persist
resource="http://bugzilla.mozilla.org/attachment.cgi?id=58879&amp;action=view#fld"/>
  </RDF:Description>
  <RDF:Description
about="http://bugzilla.mozilla.org/attachment.cgi?id=58879&amp;action=view#fld"
                   value="see?" />
to your localstore.rdf gives you a the value, but you can't change it.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Just a note about this bug.  It may seem minor, but having this work could be a
huge benefit.  Now instead of having to worry about persisting user preferences
or data I just throw the persist tag on there and a huge chunk of work is done
for me and in a general (read well tested) way. 

This would be a wonderful fix to have.
This is making life difficult for extension developers.

Clearing Mozilla 1.1 target; changing hardware/OS -> All
OS: Solaris → All
Hardware: Sun → All
Target Milestone: mozilla1.1alpha → ---
For some weird reason, the "value" attribute specifies the initial value of the text control and doesn't change to reflect the changes to value property. This has been like that for a long time for both XUL and HTML. So this is wontfix, in my opinion, and extension authors need to set an attribute from the value property on unload.
Summary: xul:textbox.value doesn't persist → xul:textbox.value doesn't persist (because value attribute isn't always equal to the value property)
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
Assignee: hyatt → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: