id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
9786	Silent try-catch blocks that covers more than a native code should log caught errors	Piotrek Koszuliński		"http://dev.ckeditor.com/ticket/9706#comment:4

Again we were close to miss some important error because it was thrown in silent try-catch (this time in selectionChange listener).

We should review all try-catches in code and:

1. if that's a try-catch that covers only one critical line of native code that can throw an error which we cannot handle differntly, then it's ok.
2. all other try-catches should be:
  1. removed (may be unsafe, because we'd have to test what'd be the impact).
  2. logged - we need logs (at least in DEV mode - we can introduce CKEDITOR.DEV flag with %REMOVE_LINE% annotation) of caught errors. Now it'd be unsafe to unwrap e.g. selectionChange listeners, so at least we should know about what was caught."	Bug	confirmed	Normal		General	4.0