I don't believe that this can be caught becuase the error is thrown very early in the framework startup and your particular application hasn't even been started yet.
You can build custom error messages and attach them to the SICF node, but this isn't going to let you by pass the error.
The offical SAP response (from note 1294877) is that you can use the IE8 blocker toolkit provided by Microsoft to keep users from installing IE8.
Even if you could bypass the error or change the client string identification; IE8 isn't supported and you could run into problems and inconsistencies in the rendering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.