| Summary: | Consider to discontinue IE6 support in RAP | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chris, tbuschto |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M3 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ralf Sternberg
We agreed that 1.5 will no longer support IE6. What is left to do is remove IE6 specific javascript code. (In reply to comment #1) > What is left to do is remove IE6 specific javascript code. I've found that IE8 in Quirks mode as it does with RAP uses the same exact same rendering engine as IE6 did, just running in an IE8 tab. (That, or they decided to "emulate" browser crashes) When you force IE8 into standards mode things fail to render correctly, if at all. The application we develop is completely unusable when rendered in IE8 standards mode. I would imagine removing the IE6 work-arounds would break compatibility with IE8 unless RAP is re-worked to render in standards mode. IE8 in Quirksmode is not identical to IE6, though the difference (performance aside) is minimal. (Mostly just opacity and png support.) We would only remove code that specifically runs in IE6 only, so behavior IE8 would not change in any way. IE6 specific code has been removed in CVS HEAD. Website also updated, now IE7 is listed as lowest supported version. (1.4 still supports IE6) |