|
|
|
|
|
by kamjam
5119 days ago
|
|
From this I get
1. A server side developer (C#/Java/PHP/Whatever) trying to be a HTML designer
2. A n00b HTML designer that's not been around long enough to know the different IE box models and workarounds needed. I'd guess 2. You can get most layouts to work in IE7, and with a lot of effort, IE6 even. Agree on the security aspect, but bear in mind that the majority of home users probably have Windows Auto Updates on so they should be running IE8 (I know IE7 was a forced update for XP users, not sure if IE8 is...) So that means either a user has turned off auto updates, OR mroe likely it is a business with policies in place. There's nothing on that lexity site (at least from the demo) that couldn't be coded to work in IE7 with an conditional css include. |
|
Of course it's possible to make things work, in case of a simple layout, most of the time not even hard (note that this wasn't my point at all), but if you code in a standards-compliant, normal way, without doing anything to especially accomodate IE7, there are a number of situation where things will just not work, while working in every other browser.
Is this a problem? Yeah. I would say so. People shouldn't be supporting something and thereby supporting the continued use of a product that doesn't work unless you coddle it. What if someone is a linux user? Are they supposed to buy a windows license just to coddle to users who are hurting the web with their browsing choice?
I'm by no means an expert designer, but I've been doing HTML stuff for a decade or so, from simple to complicated. I can and do get my layouts running in IE7, but that's not the point. The point is that I shouldn't, and if someone doesn't want to, they shouldn't be criticized for that. I'm pretty tired of running a VM to test my layouts as well.