Closed
Bug 283339
Opened 20 years ago
Closed 20 years ago
Premature firing of xforms-value-changed event
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: stpride, Assigned: aaronr)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050223 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050223 Firefox/1.0+
Not sure if this is valid as the spec is not entirely clear on the matter. When
a page containing an xforms-event-changed event bound to a form control loads,
the event is triggered. Not sure if this should occur when a page loads or only
when a form control triggers the event change in which the xforms-event-changed
is bound. An example is DSTC's Stock Order at
http://xforms.dstc.edu.au/examples/dstc/stock-order.xhtml
Note: formsPlayer does not fire the event on page load, but only when the value
of the <input> changes. Novell's plugin doesn't appear to fire the event either
way (although, I have a slightly older version).
Reproducible: Always
Stephen, can you verify if this is still happening? I made up my own little
testcase (since the page that you mentioned didn't load for me) and I couldn't
recreate it. Thanks.
| Reporter | ||
Comment 2•20 years ago
|
||
After discussing this bug with Aaron, we concluded it is invalid. The firing is
from the xf:alert's and not the xforms-event-changed events.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•