|
|
Rank: Newbie
Groups: Member
Joined: 1/15/2010
Posts: 2
Points: 6
Location: Noida
|
Hi,
I am having an issue that some of my web application are being migrated from IE6 to IE8.
So there some layout issues when i open them in IE8...i just wanted to confirm that how can i use Sortsite to recognise them?
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/18/2005
Posts: 110
Points: 243
Location: Edinburgh
|
We're currently researching this. Most of the compatibility checks are for backwards compatibility (e.g. what works in Firefox version 3.0, but doesn't work in version 2.0).
Some of the checks do apply to forwards compatibility when moving from IE6 to IE8. Once I've collated the information I'll post it here.
|
|
Rank: Newbie
Groups: Member
Joined: 1/15/2010
Posts: 2
Points: 6
Location: Noida
|
Thanx for your quick reply!
Can you please tell me some of the check points that you use in sortsite to check for forward compatibility?
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/18/2005
Posts: 110
Points: 243
Location: Edinburgh
|
One of the biggest changes between IE6 and IE8 is the handling of invalid HTML markup (unclosed tags, malformed comments, etc.)
This means that some elements displayed by IE6 may just disappear in IE8 if pages contain invalid markup. You can see these validation issues listed on the Standards tab - if you've not validated your pages before you're likely to see a *lot* of issues.
The most serious validation problems trigger an error on the Accessibility tab:
"This page has markup errors which cause problems in screen readers. WCAG2 A F70"
(the same issue affects screen readers since their invalid markup error handling is not identical to IE6)
|
|
Rank: Administration
Groups: Administration
Joined: 9/30/2005
Posts: 16
Points: 24
|
The next maintenance release (3.6) will contain additional forwards compatibility checks including:
- assigning to window.event (read-only in IE8)
- using invalid HTML (unclosed tags) that render differently in IE6 and IE8
- using non-standard JSON methods
- using CSS expressions (supported in IE6/7, but not IE8 or other browsers)
- various CSS filter hacks that break in IE7 and IE8
- mixed http / https content warnings
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/18/2005
Posts: 110
Points: 243
Location: Edinburgh
|
The 4.0 release contains some new forwards compatibility checks including:
- setting event.source property (read-only in IE8)
- unclosed and malformed tags that IE8 handles differently to previous releases
- non-standard JSON methods
- using CSS expressions (supported in IE6 and IE7 but not IE8 standards mode or other browsers)
- various CSS hacks that work in IE6 but break in IE7 and IE8
- detect pages that display HTTP and HTTPS mixed content warnings in IE8
(the 3.6 maintenance release was replaced by the 4.0 release)
|
|
|
Guest |
