How Can I Identify Compatibility Issues in MSIE 8?

  • Thread starter Thread starter davee123
  • Start date Start date
Click For Summary
SUMMARY

This discussion focuses on identifying compatibility issues in MSIE 8, particularly regarding the handling of HTML tables with rowspan attributes. The user experiences layout problems when using collapsible rows, which work correctly in other browsers but fail in MSIE 8 due to its inability to automatically adjust rowspan when rows are hidden. The proposed solution involves creating a JavaScript function to manually adjust the rowspan for MSIE 8, while ensuring it does not affect other browsers. The issue is characterized as a potential bug in MSIE 8 rather than a compatibility issue.

PREREQUISITES
  • Understanding of HTML table structures and rowspan attributes
  • Familiarity with JavaScript for DOM manipulation
  • Knowledge of browser compatibility issues, specifically with MSIE 8
  • Experience with CSS display properties
NEXT STEPS
  • Research how to implement the "X-UA-Compatible" header in HTML
  • Learn about JavaScript methods for adjusting table row properties
  • Explore CSS techniques for managing table layouts across different browsers
  • Investigate browser-specific bugs and features in MSIE 8
USEFUL FOR

Web developers, front-end engineers, and anyone troubleshooting compatibility issues in legacy browsers, particularly those dealing with MSIE 8 and HTML table layouts.

davee123
Messages
671
Reaction score
4
MSIE 8 "Compatibility View"

Ok, I have a webpage. Looks fine in Firefox, MSIE 7, etc. But MSIE 8 barfs it into a horrible mess.

BUT! It shows me a button called "Compatibility View" that magically fixes the problem.

... That's great and all, but I'm not about to go telling our clients to click their "Compatibility View" button to fix the problem. How can I tell what MSIE 8 is doing in "Compatibility View" mode? Is there a way to highlight in the HTML/CSS/JS source code what it thinks is the problem for compatibility?

DaveE
 
Computer science news on Phys.org


Give a link to the page and I'll check it out. You could add the "X-UA-Compatible" header to force compatibility mode, but you should really find out what is the problem and fix it.
 


Greg Bernhardt said:
Give a link to the page and I'll check it out. You could add the "X-UA-Compatible" header to force compatibility mode, but you should really find out what is the problem and fix it.

Unfortunately, I can't give out the URL, since it's only for paying customers of our company, but I do think I've found the issue:

I have a table with multiple rows. It's actually a table of holidays. So the first column shows the date of the holiday, and the next few columns give the details for where the holiday applies to (country X, market Y, etc). The first column's cells often have a multiple rowspan-- that is, a particular date's holiday is applicable to multiple countries and multiple markets.

However, we wanted to make the rows collapsible so that it can show a single holiday compacted to a single row. Solution? Make a Javascript function that toggles the visibility and display of a row. Great! Works in MSIE 6, 7, Firefox, Opera, and Chrome.

But in MSIE 8, what's happening is that the rowspan is getting us into trouble. That first cell shouldn't get hidden, even though it's displaying across the hidden row. In all the other browsers, when you hide a row (probably when you set the display property to "none"?), the first cell's rowspan gets adjusted automatically. In MSIE 8, it does NOT get adjusted, and it decides to re-render the table, forcing that first cell's rowspan down so that the cell gets displayed in subsequent rows.

So, the next solution will be to do the rowspan adjustment in JavaScript. BUT, we'll have to turn it off for all the OTHER browsers, since I expect it will cause problems in other browsers (including MSIE 6 and 7). So it'll have to ONLY go in for MSIE 8.

And given that this seems to work in EVERY other browser, I'm of the mind to think that it's a bug in MSIE 8 rather than a compatibility issue. Granted, it could be that not doing the automatic adjustment is a FEATURE, not a bug, since it gives more control over the table layout, but if so, I would hope that there would be some sort of CSS flag to trigger it, rather than being the default action, which is now in contrast to how it's been done everywhere else. Some CSS flag like "span-adjust: auto;" or something. But I haven't seen any mention of anything like that.

DaveE
 

Similar threads

Replies
15
Views
11K
  • · Replies 3 ·
Replies
3
Views
2K
Replies
7
Views
9K
Replies
2
Views
2K
Replies
3
Views
2K
  • · Replies 15 ·
Replies
15
Views
7K
Replies
4
Views
4K
  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 4 ·
Replies
4
Views
8K
  • · Replies 3 ·
Replies
3
Views
780