Closed
Bug 287714
Opened 20 years ago
Closed 20 years ago
Add console outputting of errors.
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: doronr, Assigned: doronr)
Details
Attachments
(3 files, 3 obsolete files)
|
6.78 KB,
patch
|
aaronr
:
review+
|
Details | Diff | Splinter Review |
|
11.56 KB,
patch
|
aaronr
:
review+
|
Details | Diff | Splinter Review |
|
2.00 KB,
application/xhtml+xml
|
Details |
| Assignee | ||
Comment 1•20 years ago
|
||
Attachment #178584 -
Flags: review?(aaronr)
comments: XformsUtils::ReportError(): - Why have to clone aElement? Why can't you serialize aElement directly instead of using tmpNode? - Should we log empty strings? I'd vote no which would require an extra test in here. nsXFormsUtils.h: - you need to add comments to the ReportError declaration.
| Assignee | ||
Updated•20 years ago
|
Attachment #178584 -
Attachment is obsolete: true
Attachment #178584 -
Flags: review?(aaronr)
| Assignee | ||
Comment 3•20 years ago
|
||
Attachment #178804 -
Flags: review?(aaronr)
+ // if a context was defined, we clone (not deep) it, serialize it and append
+ // to the message.
+ if (aContext) {
+ nsCOMPtr<nsIDOMSerializer> ds = do_GetService(NS_XMLSERIALIZER_CONTRACTID);
+ if (ds) {
+ nsAutoString contextMsg;
+ nsCOMPtr<nsIDOMNode> tmpNode;
+ // SerializeToString always does a deep serialize, so we do a non-deep
+ // clone so that we don't serialize any children.
+ aElement->CloneNode(PR_FALSE, getter_AddRefs(tmpNode));
+
Shouldn't you be cloning aContext and not aElement?| Assignee | ||
Updated•20 years ago
|
Attachment #178804 -
Attachment is obsolete: true
Attachment #178804 -
Flags: review?(aaronr)
| Assignee | ||
Comment 5•20 years ago
|
||
Attachment #178828 -
Flags: review?(aaronr)
Attachment #178828 -
Flags: review?(aaronr) → review+
| Assignee | ||
Comment 6•20 years ago
|
||
Attachment #178959 -
Flags: review?(aaronr)
| Assignee | ||
Updated•20 years ago
|
Attachment #178959 -
Attachment is obsolete: true
Attachment #178959 -
Flags: review?(aaronr)
| Assignee | ||
Comment 7•20 years ago
|
||
Attachment #178965 -
Flags: review?(aaronr)
| Assignee | ||
Comment 8•20 years ago
|
||
Comment 9•20 years ago
|
||
r=me
Comment 10•20 years ago
|
||
Comment on attachment 178965 [details] [diff] [review] better patch I'd really like to see a way to log errors and warnings to the console too, instead of just "messages". IRC says that should just be a flag on the nsIConsoleMessage. That way we can have a easy way to pick out "fatal errors" where we stop processing the form. But we can do that in a seperate bug if you want. r=me
Attachment #178965 -
Flags: review?(aaronr) → review+
| Assignee | ||
Comment 11•20 years ago
|
||
Using nsIConsoleMessage would mean I would have to create a nsIXFormsError that implements it and all. Doable, but I think warnings is good enough for now :)
| Assignee | ||
Comment 12•20 years ago
|
||
checked in.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 13•20 years ago
|
||
or you can CI http://lxr.mozilla.org/seamonkey/source/js/src/xpconnect/idl/nsIScriptError.idl#101
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
•