> > Hi everyone, re the new css. We discussed this aways back on the dev > > list and I said I was working on a new framework that could be used for > > the template, but that I did not think it would be ie-6 css compatible > > and asked for opinions. At that time, it seemed everyone was fine with > > no ie6, but of course at that time, ie 8 was also supposed to be out by > > now. > > > notice that *think it would not* is very different from *it will break > and we should warn you to upgrade*, but the clarify I think the best > way today is to code things in a real browser, and then "fix" it for > the bad ones. Which I think is the stage we are at now.
Yeah, I agree. I knew the stretched absolute positioning was not going to work, but didn't realize the havoc the daisy chained selectors would cause. > > > Basically, what I did make a system whereby you can change a geometric > > measurement in only *one* place, and have the all the other components > > respond properly. So changing the widths or height or margin of the > > outer container will reflow all other components in nice alignment. I > > have never seen this work in any IE6 supporting css setup, there is > > always the necessity to change numbers in several places, especially if > > combining floating three column layouts with absolutes and so on. I also > > kept *all* layout and presentation controls out of ids, so that users > > can use semantic ids as they see fit. > > > That's really nice, I have dream about that for quite some time. Cool, that's at least some motivation to keep working on the concept. =) > > > That said, I won't be at all offended if we shelve it for now until ie8. > > That's cool, but I'll warn you that porting it is not pretty, I just did > > it for my own site here: http://www.flyingnotfalling.com ( that's me! ) > > > That site looks very nice, very professional indeed. As for shelving > it I don't think so I'll prefer to have a ie6 workaround or simply a > quickstart template for ie6 You should be able to compare the xhtml/css files from the tg template and flyingnotfalling to see what had to be done. Basically all layout behaviour that depended on things like .main.region.fixed-x-fixed-y had to be replaced with ids like #main-region > I think we should try in this order > a- try to make it work with some conditional comments I'm pretty sure that won't work, at least I tried long enough to abandon it myself! > b- make a separate id layout template that's what I did for fnf, recommended > c- fix it with JS? that was my *original* intent, to just have a js file for ie6 make the corrections, but the selector problem sunk that one Thanks for the interest! Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
