What you succeed in doing with this method of handling browser compatibility is take something that MAY NOT work, and turn it into something that DEFINITELY DOESN'T work. I know for a fact that this browser works just FINE with the template, because if I change the browser's identifier to claim it is a different version the template works. More important, you've removed the decision from me. This is the kind of arrogant, unthinking, over-controlling, poor user interface design that has users hating the product line and has help cost you the market.
The appropriate way to handle an unknown browser type is simply to put a highlight bar at the top or bottom of the page -- floating so it stays there if you like -- that says "WARNING: Your browser may not be compatible with the content on this page. For a list of supported browsers, please click here." Then, let the user go about his or her business and get their work done.
Comment Entry |
Please wait while your document is saved.
Are you using Chrome? If so there is an notes.ini setting to prevent the
warning, it works fine but is not certified.