Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334758 - [Client] Catch javascript errors outside of server-responses
Summary: [Client] Catch javascript errors outside of server-responses
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 06:21 EST by Tim Buschtoens CLA
Modified: 2011-02-07 06:27 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2011-01-19 06:21:22 EST 
Currently all javascript-errors that occur outside of the eval of a server-response dont get catched and only show up in the console. It would be difficult to catch an process ALL javascript errors, but at least those that occur in common dom-events (like mouse-, key- and most timer-events) should create a error page like the one used on the Request.js.
Comment 1 Tim Buschtoens CLA 2011-02-07 06:27:03 EST 
Fixed in CVS HEAD.