Re: [infrastructure] [Drupal.org problem] IE7 Compatibility issue needs your attention
Hello all, Why do they think the problem is on our side? Unless they are addressing an issue with our themes not adhering to standards, they don't have a valid point. I suspect this IE7 release will break many sites, just to force people to code in a way only this browser can understand. My suggestion is that we need to keep ourselves very skeptical about their incompatibility reports and keep focusing on standards. If they want to release a broken browser that's up to them. Let's see what those supposed incompatibilities are.
Hello,
My name is Keryn Mark and I am part of the Internet Explorer 7 Compatibility team at Microsoft. We have discovered IE 7 compatibility issues with your website and we want to work with you to resolve these issues as soon as possible. I would appreciate any contact information you can provide for your website maintenance. I would like to forward you further details on the compatibility issues we've identified in your site and how to resolve.
Thank you for your time!
Best Regards, Keryn Mark Program Manager, IE7 Compatibility Team Microsoft a-kerynm@microsoft.com -- [ infrastructure | http://lists.drupal.org/listinfo/infrastructure ]
= = = = = = = = = = = = = = = = = = = = Best regards. Edgard Durand http://capmex.biz 2006-01-20
Keryn and I are talking. I have screenshots and the various hacks and just asking for information that is not MS confidential to be published. Last time I checked the theme on Drupal.org did not validate so I think we need to be careful about accusations of incompatibility with standards until we see the evidence. Cheers, Kieran On Jan 20, 2006, at 10:25 AM, Edgard Durand wrote:
Hello all,
Why do they think the problem is on our side? Unless they are addressing an issue with our themes not adhering to standards, they don't have a valid point.
I suspect this IE7 release will break many sites, just to force people to code in a way only this browser can understand.
My suggestion is that we need to keep ourselves very skeptical about their incompatibility reports and keep focusing on standards. If they want to release a broken browser that's up to them.
Let's see what those supposed incompatibilities are.
Hello,
My name is Keryn Mark and I am part of the Internet Explorer 7 Compatibility team at Microsoft. We have discovered IE 7 compatibility issues with your website and we want to work with you to resolve these issues as soon as possible. I would appreciate any contact information you can provide for your website maintenance. I would like to forward you further details on the compatibility issues we've identified in your site and how to resolve.
Thank you for your time!
Best Regards, Keryn Mark Program Manager, IE7 Compatibility Team Microsoft a-kerynm@microsoft.com -- [ infrastructure | http://lists.drupal.org/listinfo/infrastructure ]
= = = = = = = = = = = = = = = = = = = = Best regards. Edgard Durand http://capmex.biz 2006-01-20
_______________________________________________ themes mailing list themes@drupal.org http://lists.drupal.org/mailman/listinfo/themes
Hello there! I'm fresh to this list, but don't want to intruduce my self. Edgard Durand wrote:
Why do they think the problem is on our side? Unless they are addressing an issue with our themes not adhering to standards, they don't have a valid point.
I suspect this IE7 release will break many sites, just to force people to code in a way only this browser can understand.
My suggestion is that we need to keep ourselves very skeptical about their incompatibility reports and keep focusing on standards. If they want to release a broken browser that's up to them.
Let's see what those supposed incompatibilities are.
The Drupal Theme/Page has some flaws, Tidy gives me this on the drupal.org Startpage: Zeile 61 Zeichen 74 - Warnung: unescaped & or unknown entity "&task" Zeile 61 Zeichen 84 - Warnung: unescaped & or unknown entity "&id" Zeile 190 Zeichen 54 - Warnung: <wbr> is not approved by W3C Zeile 195 Zeichen 110 - Warnung: <wbr> is not approved by W3C Zeile 201 Zeichen 102 - Warnung: <wbr> is not approved by W3C Zeile 217 Zeichen 1206 - Warnung: <wbr> is not approved by W3C Zeile 217 Zeichen 1626 - Warnung: <wbr> is not approved by W3C Zeile 15 Zeichen 85 - Warnung: <link> inserting "type" attribute Zeile 21 Zeichen 9 - Warnung: <a> attribute "href" lacks value Also some Pages with have problems on 1024x768. I know it's Microsoft, but if they really want to commit Bugreports, Screenshots, workarounds or anything else to make the site better visible/useable for the upcoming 80% of all webusers. Why should anyone stand against it. Also IE7 should support the most Webstandards at startup, so it should be easy to support this little peace of crap.
Hello all, As a CSS developer and Drupal themer, I have been talking with Keryn at Microsoft about IE7, along with Kieran (Civicspace) as well. Their browser *does not* break the layout of the site and does adhere to the standards. The problem lies in the article Edgard linked to. Essentially, Microsoft is cleaning up their parser, so it will start to *finally* be able to parse valid CSS and CSS2 and etc. As a result, some widely known IE specific hacks no longer work. In the case of Drupal.org, this is quite simple. The hack on Drupal.org is used to align the menu tabs, that is the only thing broken, it is quite small problem actually. In my experience, this hack is *not* needed, if the CSS was more cleverly designed, the hack would have not have been needed at all, as this is a simpler situation to fix. I actually applaud IE for *contacting us* and alerting us to the fact. It will not be hard to fix Drupal so it doens't rely on the hack and when IE7 *does* come out, we won't get hounded with lots of forum posts saying "Drupal looks bad in my browser!". Not to mention, fixing this hack would bring Drupal.org itself closer to fully validating. ted On 1/20/06, Edgard Durand <privacy@capmex.biz> wrote:
Why do they think the problem is on our side? Unless they are addressing an issue with our themes not adhering to standards, they don't have a valid point.
I suspect this IE7 release will break many sites, just to force people to code in a way only this browser can understand.
My suggestion is that we need to keep ourselves very skeptical about their incompatibility reports and keep focusing on standards. If they want to release a broken browser that's up to them.
Let's see what those supposed incompatibilities are.
participants (4)
-
Christian Berg -
Edgard Durand -
Kieran Lal -
Theodore Serbinski