The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
You may want to look at http://remysharp.com/2010/10/08/what-is-a-polyfill/ and https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills.
Personally I don't work on websites, but on web apps, and use http://qooxdoo.org/. But the framework also has website development support, possibly integrating much stuff listed in the second page linked to above already - I have no idea, since I don't use their website stuff, but judging from what their desktop stuff looks like, they build powerful, solid and comprehensive solutions - nothing half-baked.
There is a difference between having to support IE7, and having to make it look good in IE7.
If I were you I would create an adaptive layout that looks good in modern browsers and works on different sized windows to solve the mobile device vs. desktop problem.
For the layout details, though, don't limit yourself to CSS that works in IE7. Just accept that things may look not quite right. It's not too hard to make something that works in IE7, though you'll go crazy trying to make it look exactly the same (unless you want it to look like it's 2005 in ALL browsers). If your organization can accept that using an old browser means their web sites aren't going to look like a modern browser, and may have layout issues, then I'd go with that approach.
If they expect everything to look snappy in IE7 too, then you're screwed.
> If they expect everything to look snappy in IE7 too, then you're screwed.
That's where we were for this release, and what I'm trying to avoid in the future.
For anyone that still needs to estimate what it would take a competant designer with a lot of CSS experience to make a site that looks good in Chrome/FF look pixel perfect in IE7 a good estimate is +100-150%.
And, yes I mean multiply your IE7 estimate by 2 or 2.5
And, no I'm not the one that did it (I just did the web application).
My strategy is to support the latest 4 major browsers, which usually are IE, Firefox, Chrome and Safari, then support the 3 most important mobile web browsers, Safari on IOS, Android Browser, Windows Phone IE. For backward compatibility a focus on functionality over design, it should work but it may not look exactly the same and usually i test on the last 4 major versions of a browser, when available.
We are quite similar. We will support whichever browser/version we choose but will get to N% of observed users. This applies for desktop and mobile seperately (although percentages change and measurement is by country). For internal-use corporate customers we name the versions that make up the N% of browsers/devices and if you want something not on the list you pay to get it added. Otherwise we end up spending lots of effort supporting X.Y.Z for 0.008% of user base. Using percentage rather than direct naming means we guarantee to keep adapting to market trends.
LOL. Entertaining. A perfect example of how many people debate politics.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
Last Visit: 31-Dec-99 18:00 Last Update: 26-May-17 15:45