YES! like that 
This forum post has been removed
MSIE 6 was a terrible version of a not too good browser anyway. It should no longer be used.
Joseph
Of course you're right. Actually, I don't use it, it's only still installed on my computer
But in fact IE 6 is still used by 17 % of Internet users, especially in Asian countries (http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2 ).
Frank
Most likely nobody has tried to create that theme for Old Browsers ( = IE ) yet - but it might be time to simply stop supporting IE6 in moodle 2. No more IE hacks - never again 
( partly joking - the situation in Asia/China and in some African countries has not changed even if Microsoft itself has tried to kill IE6 with recent campaigns )
And implementing YUI2/YUI3 scripts obviously has some issues with IE...
It's actually becoming a bigger problem here as a larger middle class is developing with more disposable income- they're buying new computers that come preloaded with IE7 or IE8 making these sites unavailable.
Essentially this problem will resolve itself, nobody will have IE6 on their computer anymore soon enough, either via a hardware/software purchase, or a hardware crash.
This forum post has been removed
Quote:
"Moodle now supports the Yahoo! user interface library which includes unobtrusive JavaScript as one of its primary design goals"
This forum post has been removed
It's one of those strange bugs that nobody has been able to fix yet - http://tracker.moodle.org/browse/MDL-22372
obviously some javascript of moodle (yui/ajax/navigation/blocks ???) has some event handler that causes delay until you move mouse... if javascript is disabled IE loads css without problems and if javascript is enabled css might be loaded twice: first the "normal way" - then all css breaks (in IE) and you need to move mouse over side blocks and content to get rest of css rendered... right ?
I'm just chiming in on this one with a few interesting points as I do like where this discussion is going and all the great points that are coming out about the love affair that used to exist with IE6.
First up the standardold theme is going to be converted to a theme that works on IE6. It will use the old table layout rather than floating divs and will be based on the standard theme to ensure that we don't end having to maintain another theme just for IE6. This task is currently on my todo list as part of MDL-21862.
Second there is the now the ability to select a theme for modern browsers and a theme for old browsers. This should be of great use when using Moodle in an environment where some or all users are using IE6 or 7 (old browsers so far) as a theme that is known to work can be selected for them specifically without having to compromise the experience of users with standard supporting reasonably bug free browsers.
Third there is a myriad of problems leading to the numerous issues still being experienced within IE 7/8. The more I look into this the more I stumble upon. As I think Mauno mentioned the peek-a-boo bug is a big one at the moment, however there are several others as well, for those who have xml strict headers turned on you will have noticed the GOUC (Glimpse Of Unstyled Content) bug, and the dock causing jumps when blocks have been docked are just two more.
Fingers crossed solutions to all of these can found within the next week or two
And finally a BIG thank you to everyone who is helping out with the themes
Cheers
Sam
This forum post has been removed
Every school I've attended, or worked for has had minimum requirements for using their system, some more aggressive than others, but mandating support for systems that are over 12 years old...
Please see And as stated above IMHO Moodle 2.0 should at least degrade gracefully for users of IE6.
It's a different "BUG", Frank!
Sam fixed the "onMouse even jumping YUI IE bug" and creating a moodle 2.0 theme that can be used with IE6 just needs a volunteer themer to design an IE6 theme that does not use any features of modern browsers...
This forum post has been removed
And even worldwide IE6's market share is that of Opera, Safari and Chrome combined.
So sniffing at IE6 is IMO a developer and U.S./Europe centric perspective.
Even if you don't follow this rationale we might get into serious trouble regarding Accessibility if we rely too much on bleeding edge JavaScript technology for such basic functions as menus and navigation.
Old stats, Frank?
Worldwide stats for IE6 have gone down to 9% since last summer and eventually IE6 will vanish also in Asian and African markets...
It's not actually only a design or accessibility problem - it is also a problem of outdated security - try to google for example "You wouldn't drink nine year-old milk, so why use a nine year-old browser?" campign by Microsoft from May 2010...
Maybe we could try to get standard theme at least partly functional for the last remaining ie6 users.
I used one day in testing different themes with IE8 Quirks mode and tools like http://www.onderhond.com/tools/ie6fixer/ (based on 5 main css bugs of IE6) http://www.onderhond.com/blog/work/ie6-core-bug-fixing together with all css tags of standard theme - but it was not giving good enough results.
Finally I took just the same Quirks mode and checked main screens with IE8 developer tools and it looks like adding the following IE6 hack tags (that do not have influence to other browsers) to Standard theme file css3.css make IE6 relatively functional with Standard theme. But NOTE: I did not yet test these tags with original IE6 (my wife has one left in an old Windows 2000 PC...I can test it tomorrow) and with different resolutions. Still if these tags work only in IE6 and they don't cause trouble to other browsers - and knowing that some people may have also Mac version of IE6... - here those magical star hack tags are, asterisk * is part of those tags :
* html .block {width:100%;}
* html .header{height:auto;}
* html .loginform {display:inline-block;}
* html .calendar-controls {display:inline-block;}
* html .collapsed {display:block;}
* html .depth_3 {display:block;}
* html .jsenabled .block_navigation .block_tree .collapsed .tree_item.branch {padding-left:10px;}
* html #region-main{overflow:hidden;zoom:1;}
(Note also that Theme designer mode must be enabled from theme settings or cache purged/cleaned/invalidated before changes take action...)
Re: Moodle 2.0 jumping about - IE6 css tags tested
Navigationitem is a transparent png image and ie6 shows black border around it. Unsufficient block width causes also vertical scrollbar effect in blocks. and minicalendar title fix seems to work differently in IE8 Quirks mode and original IE6.
Furthermore IE6 has lots of performance issues (IE6 is terribly slow!!!), some new (javascript based) elements like Navigation dock or some editor plugins that may not be fully IE6 compatible...
Frankly all members of such schools and IT support that allow/force students to use IE6 should be moved to some other job...
Re: Moodle 2.0 jumping about - IE6 css tags tested
One of the "oddities of IE6" is that line
* html .calendar-controls {display:inline-block;}
that works in IE8 Quirks mode should actually be
* html .calendar-controls {display:inline;}
in original IE6...
Anyway - each theme can support IE6 only to certain level (with the setting to use one "IE6 compatible theme" for Old Browsers in administration menu) and it's up to theme designers if they want to keep on continuing IE6 struggle with several hundreds of known IE6 css bugs and javascript incompatibilities.
Many Australian organisations (inclduding mine, a huge government department and my wife's, a large private firm) still use IE6. I have absolutely no idea why, but it's still there
Guido,
it's never too late to forget IE6 and finally upgrade the last remaining IE6 browsers to some more modern version
If your IT Support Professionals still hesitate you could tell them for example that IE6 has over 20 unpatched vulnerabilities which can be exploited by malicious people to disclose potentially sensitive information or to compromise a user's system.
