Re: [WSG] This IE8 controversy

2008-01-30 Thread Patrick H. Lauke
Michael Horowitz wrote: I would assume any professional developer will test any application they currently support with IE 8 when it comes out. I'm sure I will get a lot of business from new clients who need their sites updated to support whatever changes MSFT makes. But, since IE8 will by

Re: [WSG] This IE8 controversy

2008-01-30 Thread James Bennett
On Jan 30, 2008 1:31 AM, Thomas Thomassen [EMAIL PROTECTED] wrote: They don't want to default to IE8 rendering because of what happend with IE7. It broke website. Not only that but IE is used so much outside the browser as well. It's a platform. Intranet apps. HTA apps. Even help files uses

Re: [WSG] This IE8 controversy

2008-01-30 Thread Patrick H. Lauke
Christian Snodgrass wrote: It's more likely (assuming they get the info about the meta-tag out there) that new sites will be developed using this meta-tag and standards-compliance. Eventually, the old sites will be replaced with new ones built in this fashion. Then, when they finally just

Re: [WSG] This IE8 controversy

2008-01-30 Thread Chris Knowles
Thomas Thomassen wrote: You don't have to modify every single HTML you publish. You can set the HTTP header for HTML files on your server and off you go. What I've yet to hear from people who don't like the solution is a realistic alternative. Letting the sites break is not an

Re: [WSG] This IE8 controversy

2008-01-30 Thread Katrina
Thomas Thomassen wrote: You don't have to modify every single HTML you publish. You can set the HTTP header for HTML files on your server and off you go. Don't forget the nasty gotcha: save that page on your own computer, load it back up and suddenly it looks different (as the browser doesn't

Re: [WSG] This IE8 controversy

2008-01-30 Thread Gunlaug Sørtun
Well, apart from that I don't like IE/win version targeting one bit, if MSIE uphold this version targeting strategy in future versions, we may as well use it to our advantage. Sidelining IE/win while designing for standards and better browsers, doesn't have to become a problem for designers or

RE: [WSG] This IE8 controversy

2008-01-30 Thread michael.brockington
One question that I have yet to see anyone ask is: How good will IE8 actually be? If it is perfect, then there is no need to worry about future versions... I also haven't seen anyone mention the fact that we have yet to get rid of IE5 completely - I know of at least one large organisation (not my

Re: [WSG] This IE8 controversy

2008-01-30 Thread Andrew Maben
On Jan 29, 2008, at 7:38 PM, Casey Farrell wrote: IE8 _will_ be the most popular web browser it ain't necessarily so... first of all prevalent is not equivalent to popular, but IE was not always the most prevalent browser, and is once again losing some of the market share that it unfairly

RE: [WSG] This IE8 controversy

2008-01-30 Thread James Leslie
It is the best solution they can come up with that won't destroy everything that has been created in the past. Adding one line of code to each of your pages is a lot more cost effective and time saving then all of the hacks we currently have to do to get it to display properly in IE6 and IE7.

Re: [WSG] This IE8 controversy

2008-01-30 Thread Andrew Maben
On Jan 29, 2008, at 10:10 PM, Jermayn Parker wrote: and then we will see the infamous pre-2000 days with websites reading: This is best viewed using Internet Explorer 6 Would it be so bad if this was This site is best NOT viewed with IE?? Come on - Let's not break the web - it's already

RE: [WSG] This IE8 controversy

2008-01-30 Thread James Leslie
I think we will be able to 'ignore' IE7 way before IE6 due to Microsoft being able to (presumably) force upgrades of IE7 to IE8, but still being stuck with IE6 in the way we are now on older OS's. Though IE8 rendering like IE7 by default means we will have to fix for that And no doubt

Re: [WSG] PLease remove me

2008-01-30 Thread veine
Hello; In every email you get there is an unsubscribe link at the bottom ;) http://webstandardsgroup.org/join/unsubscribe.cfm On 30 Jan 2008 at 11:25, Datatank wrote: Please remove me from this list. thanks [EMAIL PROTECTED]

Re: [WSG] This IE8 controversy

2008-01-30 Thread Thomas Thomassen
- Original Message - From: Katrina [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Wednesday, January 30, 2008 9:17 AM Subject: Re: [WSG] This IE8 controversy Thomas Thomassen wrote: You don't have to modify every single HTML you publish. You can set the HTTP header for HTML

Re: [WSG] This IE8 controversy

2008-01-30 Thread Thomas Thomassen
Not every site has a webdesigner constantly maintaining it. Retroactively editing the millions of existing pages out there will cost an enourmouse amount of money. Fitting a meta tag into existing documents isn't as easy as implementing it into new ones. - Original Message - From:

Re: [WSG] This IE8 controversy

2008-01-30 Thread Patrick H. Lauke
Thomas Thomassen wrote: Not every site has a webdesigner constantly maintaining it. Retroactively editing the millions of existing pages out there will cost an enourmouse amount of money. Fitting a meta tag into existing documents isn't as easy as implementing it into new ones. Then change

Re: [WSG] This IE8 controversy

2008-01-30 Thread Thomas Thomassen
By the sound of it, IE9 will default to IE7 for documents with proper strict doctype and IE6 for documents with invalid or missing doctype. Just like IE8. Regarding what you said about X-IE9-Compatible, X-IE10-Compatible: No, it would be meta http-equiv=X-UA-Compatible content=IE=9 / if the

Re: [WSG] This IE8 controversy

2008-01-30 Thread Karl Lurman
Damn, this is the second time in the last two days I have replied to something via the WSG instead of to the person I really meant to send it to. Argghhh GMAIL! Or perhaps its just silly user error... :) Sorry everyone!!! On Jan 30, 2008 3:47 PM, Mark Harris [EMAIL PROTECTED] wrote: Karl

Re: [WSG] This IE8 controversy

2008-01-30 Thread Christian Snodgrass
Yes, I agree. Part of our job is putting up with the stupidity that MS gives us and making it work. We don't just get to say No, we won't support IE anymore, at least, not if you plan on keeping clients. Is this solution perfect? No. Is this solution acceptable? Yes. Could it be worse? Hell

Re: [WSG] PLease remove me [SEC=UNCLASSIFIED]

2008-01-30 Thread dean . turner
Return Receipt Your Re: [WSG] PLease remove me document:

Re: [WSG] PLease remove me [No Protective Marking]

2008-01-30 Thread Anastasia . Lipapis
Return Receipt Your Re: [WSG] PLease remove me [No Protective Marking] document:

Re: [WSG] Windows on a Mac

2008-01-30 Thread Christian Snodgrass
On an Intel-based processor, you should be able to actually install Windows onto a Mac machine. I've never personally tested this, but it makes sense to me. If that is the case, then it will function just like Windows on any other PC build, so you can run anything that you would normally run.

Re: [WSG] Windows on a Mac

2008-01-30 Thread Christian Snodgrass
Check out this: http://www.apple.com/macosx/features/bootcamp.html Tim MacKay wrote: Hi List, If this discussion is outside the scope of this group I apologize, I know it was touched on a couple of weeks ago. Please email me off list if you feel it’s more appropriate. I’ve recently had my

Re: [WSG] Windows on a Mac

2008-01-30 Thread Chris Broadfoot
Tim MacKay wrote: Hi List, snip I have a few questions about the Windows environment on the new Macs. Specifically, can I run things like Microsoft Visual Studio? Flash Develop? Can I download and run .exe files? Is the Windows environment on Macintosh a true Windows environment and is it

RE: [WSG] Windows on a Mac

2008-01-30 Thread Andrew Boyd
Chris Broadfoot [EMAIL PROTECTED] wrote: Both of them provide seamless (as much as it can be) integration between OSX and Windows, however if you run Bootcamp, you'll be booted into Windows and need a restart to get back into OSX. Hi, probably getting a little offtopic, and certainly too

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-30 Thread David Hucklesby
On Tue, 29 Jan 2008 21:37:26 +1100, Andrew Freedman wrote: Conflict between Mime Type and Document Type http://www.bigbaer.com/css_tutorials/css.image.text.wrap.htm Yah. DOCTYPE is XHTML 1.1, which should only be served as XML. I suggest HTML 4.01 or XHTML 1.0 instead, unless you want to

Re: [WSG] Conflict between Mime Type and Document Type

2008-01-30 Thread Thomas Thomassen
Why sniff out browsers that accept XML? If the document is marked as XHTML 1.1 it should allways be sent as XML. Though, I have seen people sniffing out browsers and using server side scripting to change the doctype. XHTML 1.1 to browsers than supports it, and XHTML 1.0 with the html mime to

Re: [WSG] PLease remove me

2008-01-30 Thread Stijn Audooren
Return Receipt Your Re: [WSG] PLease remove me document :