| Category | Issues | Root cause | |
| CSS or Cascading Style Sheets issues |
| Due to browser rendering behavior | |
|
| UI alignment issues | Due to browser rendering behavior | |
|
| Scrollbar issues on pop-up’s | Due to browser rendering behavior | |
|
| Issues due to absolute positioning or relative positioning of div. (Overlapping of base page and div) | Due to browser rendering behavior | |
|
| Dropdowns do not work | Due to classes defined in style sheet not supported in different browsers | |
|
| Popups do not display | Due to classes defined in style sheet not supported in different browsers | |
| JQuery issues or JAVA script issues | Images on any buttons do not appear | Due to classes not supported in different browsers | |
|
| Images on any panels do not appear | Due to classes not supported in different browsers | |
|
| Java Script properties issues | | |
|
| Dropdowns do not work | Due to classes defined in style sheet not supported in different browsers | |
|
| Popups do not display | Due to classes defined in style sheet not supported in different browsers | |
| Common | Text wrapping issues in textboxes | | |
| | Resizing of windows or resizing of textboxes | | |
| | Button functionality issues | | |
| | Tab order issues | | |
| | Browser Support for Graphic Formats Old and very old browsers do not support JPEGs PNG is an upcoming format supported by newer browsers | | |
| | Tables Cellspacing, Cellpadding, and border issues. | | |
| | Screen Variations screen size and settings issues | | |
| | Default Character Width Size Different platforms use a different default character width size. You'll notice that the same text and graphics will look slightly larger on a Mac than it does on a PC.
The two operating systems use a different default character width size. On the Mac, each character pixel is sized to be 1/72nd of an inch at the default 640x480 screen size. On the PC, each character pixel is sized to be 1/96th of an inch at the default 640x480 screen size. This means that a 72 pixel wide image will fill up one inch of Macintosh screen real estate—but not quite an inch of PC screen real estate | | |
| | Query string issues | | |
| | FAV icon issues | | |
| | Control ids are case sensitive in Mozilla. | | |
| | Inner HTML does not work in FF 1. Inner HTML (getting) – returns the worst markup possible 2. Inner HTML (setting) – doesn’t work on the elements you would want to dump a bunch of data into (e.g. tables and selects) | | |
| | A text node in Firefox allows only 4K data. So an XML Ajax response gets split up into multiple text child nodes instead of only one node. Its fine in Internet Explorer. For Firefox, to get the full data you either need to use node.normalize before you call node.firstChild or use node.textContent, both of which are Mozilla specific methods | | |
| | Internet Explorer does not replace or HTML char code 160, you need to replace its Unicode equivalent \u00a0 | | |
| | In Firefox a dynamically created input field inside a form (created using document.createElement) does not pass its value on form submit. | | |
| | document.getElementById in Internet Explorer will return an element even if the element name matches. Mozilla only returns element if id matches. | | |
| | In Internet Explorer if a select box has a value not represented by any of the options, it will display blank, Firefox displays the first option. | | |
| | | |
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
