|Subject:||CGI::Carp::fatalsToBrowser assumes custom handlers will also display the error message in <pre> tags|
CGI::Carp::fatalsToBrowser assumes custom handlers will also display the error message in <pre> tags, and therefore escapes any angled brackets etc. This massively reduces the flexibility of the feature, as the user may actually want to specify HTML which is handled by a custom handler specificed by set_handler. As I see it there are two ways to resolve this. 1) Only escape when a custom handler is not used - This has a disadvantage in that it may break other people's code that are relying on this escaping behaviour. 2) Have a set_html_handler which in addition to calling set_handler also sets a variable to indicate the handler can handle HTML and do not do the escaping in fatalsToBrowser when this variable is set. I'll happily provide a patch for either options if you agree that this behaviour is something that should be changed to provide greater flexibility.