There will be no more development for Atahualpa (or any other theme), and no support. Also no new registrations. I turned off the donation system. I may turn the forum to read only if it gets abused for spam. Unfortunately I have no time for the forum or the themes. Thanks a lot to the people who helped in all these years, especially Larry and of course: Paul. Take care and stay healthy -- Flynn, Atahualpa developer, Sep 2021
if you mean the very top with the skiers and the words 'race ski tracer' in 'snow' - I see it in IE8
__________________
"Tell me and I forget, teach me and I may remember, involve me and I learn." - Benjamin Franklin
Juggledad | Forum Moderator/Support
#3
Nov 11, 2009, 11:05 AM
jack96161
66 posts · May 2009
Yes -- the problem is that the majority of browsers in use world wide is still IE6, so I have to allow for it (and IE7) as well...
I noticed that this has come up in the past on this forum, (both missing logo and headers in earlier versions of IE), but there hasn't been a generic solution. When I look at the generated source that IE is trying to render, the HTML code generated by Atahualpa3.4.4 for the logo area is:
* html a.posts-icon, a.comments-icon, a.email-icon, img.logo
{
}
Any clue as to what it is about this HTML and CSS that IE6 chokes on?
[Curse You Microsoft!!!]
Thanks, Jack
#4
Nov 11, 2009, 01:03 PM
jack96161
66 posts · May 2009
OK, I did a bit of research with a friend at Mozilla who tracks these things. Hopefully, IE6 is really a dying breed. While all versions of IE still account for something like 60% of all users (and dropping daily), IE6 has dropped to 10% or less - 3-4% in many places outside the US. Firefox is at least 25% and growing rapidly -- yeah!!
Maybe we should finally stop the hours spent kludging our sites to accommodate IE6? It would sure make my life easier. Like many, I develop with Firefox, using the invaluable Firefox web designer tools, and then go back to try to make things look reasonably the same with Microslop's non-standard browsers. IE7 and now 8 do seem to be much more compatible with W3C standards and I confess I rarely try them any more - I try to keep as much MS code off my systems as possible since keeping up with the security patches of security patches consumes so much energy, stress, and bandwidth.
Some of the few former Safari glitches seem to have been corrected as well, so I'm lax in checking it as well. Could there be some light at the end of the tunnel of multi-browser tuning?