Closed
Bug 273804
Opened 20 years ago
Closed 19 years ago
unhandled xforms exceptions should get dumped to the JS console
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 290465
People
(Reporter: darin.moz, Assigned: aaronr)
References
Details
Attachments
(1 file)
2.84 KB,
patch
|
Details | Diff | Splinter Review |
unhandled xforms exceptions should get dumped to the JS console i'm not quite sure how we would implement this, but it seems like it might be a good idea.
Comment 1•20 years ago
|
||
I discussed this with smaug recently, and also think we should have a default handler of sorts, and the JS Console could be a good target. No design propoposal from me either :)
Comment 2•20 years ago
|
||
This adds a way to dump the name of the unhandled exception, but something more is needed. Document URL and maybe event target? And of course, how do we decide when an event is actually unhandled?
*** Bug 278163 has been marked as a duplicate of this bug. ***
Comment 4•20 years ago
|
||
The main question here is, how we should report the errors. If the form is invalid, we don't want to present the end user with a broken, non-functional form. Perhaps replace the page with a error page? Or an alert? We might want to send a more detailed error to the js console. Question is, can we figure out what line the error is on?
Comment 5•19 years ago
|
||
This bug seems to have two real issues: 1. add error output to js console, which is bug 287714 2. better inform user of fatal errors, which is bug 290465 So I'm duping to bug 290465. *** This bug has been marked as a duplicate of 290465 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
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
•