Ok, I object to what is happening here. Trying to fix problems with IE not rendering the site correctly/stylesheet problems/logo problems/whatever SHOULD NOT BE DONE IN THE MAIN www/ DIRECTORY
Either have another installation somewhere else and play with it, then apply the changes to the main site, Or use a locally installed copy.
If the persons responcible for the site administration don't have GNU/Linux boxes, I can offer them shell access to my personal box.
The guy has a point here. I g
The guy has a point here. I guess this is the same problem that happened long ago though, it was the other way around. Trying to display badly written HTML correctly just because IE allowed it in favour of making it 'easier' on the web developer. IMHO, we could have some CSS that's sent according to the browser identification which should fix all the issues.
Salam, Maher
That's pobably a good idea.
I'm with Maher here. To extend his point, first priority should be to a working, correct css for Real Browsers(tm), and then when someone has the time, a css for b0rked IE.
Bass at the moment, we only had Alaa working on the CSS and he was stressing, so we've agreed to delegate it to Manal and whirlpool (one he's done with exams).
Maher, wanna help? :)
--
Making the site correctly ren
Making the site correctly renderable by IE isn't necessary but recommended. New potential Linux users first explore the Linux world under Windows then try it if they find it appealing enough, they get there impression from related sites.
Anyway, if it gets us alot of trouble then we can live without it :D
BTW, You probably know this but just in case,
Disagree, IE needed
NewComer, I disagreee strongly with you.
Alot of people have linux trouble, so they post under windows (especially guys who suffer the winmodem disease). that's why IE is needed (I know it suxxx).
You got me wrong, please re-r
You got me wrong, please re-read what I've said
you don't need IE
overload
I agree that minimum support to IE is essential for several reasons. You could say essential browsability, but I don't think that we will be overloading ourselves with more work to get a non-standard compliant browser to work. The application has broken support for many things, its the application's problem.