Closed Bug 257177 Opened 20 years ago Closed 20 years ago

xforms-binding-exception thrown incorrectly

Categories

(Core Graveyard :: XForms, defect)

Other Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aaronr, Assigned: aaronr)

Details

Attachments

(1 file)

reading through nsXFormsModelElement.cpp, I came across a bug. It looks like the code will throw a binding exception if the XPath doesn't evaluate. Looking at the spec, it looks like this should be more of a xforms-compute-exception. so either need to make the errors more granular or change the exception to be a compute exception.
Summary: target for xforms-binding-exception thrown incorrectly → xforms-binding-exception thrown incorrectly
(In reply to comment #0) > It looks like the code will throw a binding exception if the XPath doesn't > evaluate. Looking at the spec, it looks like this should be more of a > xforms-compute-exception. > > so either need to make the errors more granular or change the exception to be a > compute exception. I agree, both exceptions could occur. But we need to implement the XPath extensions, so let's ignore it until then :)
Blocks: 259605
No longer blocks: 259605
Here's a patch that should dispatch the corrent events, follwing the 1.1 draft (http://www.w3.org/TR/xforms11/).
Attachment #166213 - Flags: review?(aaronr)
Comment on attachment 166213 [details] [diff] [review] Patch for the above Good code, well placed. r=aaron
Attachment #166213 - Flags: review?(aaronr) → review+
Attachment #166213 - Flags: review+ → superreview?(bryner)
Attachment #166213 - Flags: superreview?(bryner) → superreview?(darin)
Comment on attachment 166213 [details] [diff] [review] Patch for the above there are other places where we probably need to throw xforms-binding-exception, but we can take care of those separately. this looks good to me. sr=darin
Attachment #166213 - Flags: superreview?(darin) → superreview+
fixed-on-trunk
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Either this bug never actually made it to trunk, or it got lost in the move back and forth from the branch!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Now it is checked in to trunk (again)
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: