Closed
Bug 279444
Opened 20 years ago
Closed 20 years ago
wrong control becoming irrelevant
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aaronr, Assigned: allan)
Details
Attachments
(2 files)
|
1.76 KB,
application/xhtml+xml
|
Details | |
|
2.54 KB,
patch
|
aaronr
:
review+
|
Details | Diff | Splinter Review |
Running this testcase makes the wrong control disappear. This requires the
XPath patch to run.
Setting the input field value to 0 should make the trigger disappear. But
instead, the input field disappears.
|
Assignee | |
Comment 2•20 years ago
|
||
(In reply to comment #0)
> Running this testcase makes the wrong control disappear.
Admittedly, I haven't applied your XPath patch, but the described behaviour
existed in the branch some time ago, are you sure you are running trunk?
Another problem is that the the <trigger> element does not bind itself to the
binding expression, once again it's me who has not been entirely consistent.
Patch coming up.
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 3•20 years ago
|
||
|
|
Assignee | |
Updated•20 years ago
|
Assignee: aaronr → allan
Attachment #172247 -
Flags: review?(aaronr)
Attachment #172247 -
Flags: review?(aaronr) → review+
patch running on today's trunk fixes my problem and makes triggers behave
correctly when irrelevant.
|
|
Assignee | |
Comment 5•20 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•