Separate names with a comma.
Discussion in 'Tech Talk - Gadgets, Gizmos and Technology' started by deltafowler, Mar 19, 2009.
Wouldn't that be like shooting yourself while jumping off a skyscraper?
Yeah, but it's so much fun. :lol:
Here's what I get under XP SP3. Like I said... a mess! /steve
Shouldn't that be the other way around?? :sure:
You'd think so wouldn't you? So did I... however most web sites are not being designed to the latest standards so every time a new browser version comes along, IE, Firefox or anybody else, there are always little glitches...
It is scary how many websites still use Front Page:lol:
Not exactly, a lot of sites (this is what I think is happening on mine) use "hacks" in the coding specific to each browser. None of the browsers render everything perfectly and the same, so you always will have to compromise for one or a few of them.
Whether it be you design for IE and then do the workarounds for Firefox, or design for firefox, then do the work around for IE. This is for all browsers, just using IE and firefox as examples.
I think what is happening on my site is that their are some clearfix codes that only apply to IE, but in IE8 it does not need them. Problem is how to differentiate IE8 from the other IE versions and make everything work right. Like I said, this is not just IE though, I have had similar headaches working with firefox, opera, safari, etc.
Ya, it is a mess, the only way it renders properly is in compatibility mode.
I, for one, like being standardized when it comes to my software (except for CEs that is, which is really firmware anyway), and, love it or hate it, IE, in whatever variety you choose, is the current standard.
And while it may be slower and far less feature-filled than the current iterations of the other browsers, IE8 flies when compared to IE7, and it actually has some fairly useful new features.
Anyway, the key to really enjoying the IE8 experience is to have first moved from IE6 to IE7 (tabbed browsing---woohoo) and then to IE8 in order.
If 85% of the cars run on gasoline, doesn't that make it the standard?
never quite understood the arguement of IE not being compatible.. to me it means the minority is not compatible..
Its because it does not follow all the coding rules perfectly, but no browser does. They all put their own twist on it. IE just has had a bit more of a twist in the past.
still doesn't make sense to me.. 85% should be the standard..
Does it pass Acid 3? Safari 4 does and FF gets to 93
Where does this 85% number come from anyway?
I think the problem is, most people don't realize the other alternatives that are out there... or just haven't tried them. I used IE all the way up to a year or so ago... Until I tried FF... Never looked back... I've also shown quite a few friends, family, and coworkers Firefox, and all of them still use it...
try IE7 x64.. no flash, plugins or anything :hurah:
great ad blocking :lol:
Usual advice is to start by validating your code http://validator.w3.org/check?uri=w...(detect+automatically)&doctype=Inline&group=0 . It looks like most of the errors are compounded off the first one. Fix it by changing "&" to "&" inside the URL, use of <br> instead of <br /> in XHTML, also "<A " instead of "<a " (I think XHTML requires lower-case), then re-validate to see what's actually left. Some of these appear to be causing the tag mismatches flagged at the bottom of the validation report. Since IE has not previously been compatible with XHTML (IIRC IE8 is supposed to add this, but why use it when "85%" use a browser that doesn't), maybe IE8 doesn't have the same forgiveness for not quite perfect code as the HTML parser. These fixes may or may not affect IE8's rendering, but will either eliminate the code or the browser as the problem.
Ya, I have tried going that route and it is a bit tougher than just that as it is a dynamic template built on top of a dynamic CMS (Joomla). I actually did not make the template from scratch, so a lot of the core was not done by me and would take a ton of work to go through by hand...that is what really annoys me as it works fine in EVERYTHING but IE8 right now...
Those little errors (uppercase/lower case, etc.) should all still work fine. If you look, those are all errors in the content area, which is rendering just fine. The issue is in the template itself and header area, both of which pass the validation tests fine.
The validation tests are really weak when it comes to dynamic content. For example, take a look at the DBSTalk homepage (which works fine in all browsers including IE8)...108 errors found:
EDIT: Here is the page with code that validates perfectly...same issue :
All that I can speak is about my web design work. The requirements state that my visitor may be coming from a Mac or a Linux box as well as the Windows envrioment. There is no Internet Exploder for Mac or Linux. Do you think that Microsoft will bring out a browser for a competing operating system? I don't think so. And this was in January, 2007, so prior to regular web browsing on a mobile device such as a iPhone.
One of the things that I learned is that your life is much easier when you code for Firefox/Opera/Safari, then code in the exceptions. However, many of these workarounds are probably now breaking IE8 because these hacks only check for the presence of IE, not specific versions. One joke is the so-called "Holly Hack" for IE6 compatibility.
Want to know my headaches? Take a good read of the Browser Compatibiltiy Guide from Quirksmode. Take a look at some of the commands used to render pages, and how some say "Yes" to everything but IE, which is either "no" or "buggy".
And, what is Microsoft's definition of a compatibility test? "It works on most major sites." That's nice. Most major sites have full-blown web staffs which can test until they are blue in their face. I am a unpaid volunteer doing this as a learning experience, and I cannot design a customer website for each different browser and version. I rely on those standards.
Remember, too, that once Microsoft released Internet Exploder 6 years ago, it effectively was the majority browser for the world. So, they stopped development of it beyond bug fixes. It took Firefox to kick Microsoft on the side, and force it to start development again.
I agree, those hacks get annoying. The sad thing is that it goes the other ways too, if you design for IE you have to put in hacks for firefox which does some weird crap as well (the one that always gets me is the ghost line around many CSS menus). Opera in the past has also had its own bag of quirks, but it is not that widely used so it is usually less of a concern.
Also like you said, and what I am having trouble with right now, is that many of the hacks are just based on browser type, not version. So the IE hacks that were needed in the past are now applying to IE8 as well where they are not needed and just causing issues...they are still needed for the other versions of IE though.
need some help, i downloaded IE8 and all of a sudden the web page is larger than before, how do i get back to the original size of text? ido not like it. if i want to go back to IE7 how would i do that? regards..
Press the Ctrl key and roll the mouse wheel.