Closed
Bug 290308
Opened 20 years ago
Closed 20 years ago
Add expression to a few error messages
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: allan, Assigned: allan)
References
()
Details
Attachments
(1 file, 3 obsolete files)
|
5.56 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
Some of the error messages needs to have the expression generating the error appended to them.
| Assignee | ||
Comment 1•20 years ago
|
||
Attachment #180699 -
Flags: review?(smaug)
Comment 2•20 years ago
|
||
Comment on attachment 180699 [details] [diff] [review] Patch > */ > static NS_HIDDEN_(already_AddRefed<nsIDOMXPathResult>) >- EvaluateXPath(const nsAString &aExpression, >+ EvaluateXPath(const nsString &aExpression, Why this change? >-exprEvaluateError = XForms Error (10): Error evaluating XPath expression: %S >-noModelError = XForms Error (11): Could not find model for element >+exprEvaluateError = XForms Error (10): Error parsing XPath expression: %S >+exprEvaluateError = XForms Error (11): Error evaluating XPath expression: %S Shouldn't the first 'exprEvaluateError' be 'exprParseError'
Attachment #180699 -
Flags: review?(smaug) → review-
| Assignee | ||
Comment 3•20 years ago
|
||
(In reply to comment #2) > (From update of attachment 180699 [details] [diff] [review] [edit]) > > */ > > static NS_HIDDEN_(already_AddRefed<nsIDOMXPathResult>) > >- EvaluateXPath(const nsAString &aExpression, > >+ EvaluateXPath(const nsString &aExpression, > > Why this change? nsAString does not have .get(). I could also do a PromiseFlatString on the nsAString() or something? Strings still puzzle me... > >-exprEvaluateError = XForms Error (10): Error evaluating XPath expression: %S > >-noModelError = XForms Error (11): Could not find model for element > >+exprEvaluateError = XForms Error (10): Error parsing XPath expression: %S > >+exprEvaluateError = XForms Error (11): Error evaluating XPath expression: %S > > Shouldn't the first 'exprEvaluateError' be 'exprParseError' Indeed it should.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•20 years ago
|
||
Attachment #180699 -
Attachment is obsolete: true
Attachment #180706 -
Flags: review?(smaug)
| Assignee | ||
Updated•20 years ago
|
Attachment #180706 -
Flags: review?(smaug)
| Assignee | ||
Comment 5•20 years ago
|
||
Attachment #180706 -
Attachment is obsolete: true
Attachment #180712 -
Flags: review?(smaug)
| Assignee | ||
Updated•20 years ago
|
Attachment #180712 -
Flags: review?(smaug)
| Assignee | ||
Comment 6•20 years ago
|
||
Here we go again, forgot to rerun diff before uploading :(
Attachment #180712 -
Attachment is obsolete: true
| Assignee | ||
Updated•20 years ago
|
Attachment #180713 -
Flags: review?(smaug)
Updated•20 years ago
|
Attachment #180713 -
Flags: review?(smaug) → review+
| Assignee | ||
Comment 7•20 years ago
|
||
doron, could you do 2nd review and eventually check it in?
Comment 8•20 years ago
|
||
r=me, no time to check it in today though.
| Assignee | ||
Comment 9•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
•