* anatoly techtonik <techto...@gmail.com>: > > Without having looked at it closer I think using ANY framework will not > > solve > > the problem. You'd end up barking up the wrong tree. > > > > The problem seems to be located with current CSS settings a particular > > browser, here Chrome. > > > > The right way [tm] to handle this is to use a reset.css and then build > > everything from scratch. You don't want to do that with the current website. > > > > But if I were to code the CSS for the new python.org site I'd use a > > reset.css > > in any case. It set the ground for equal CSS interpretation in all browsers. > > That's something you can build from. Anything else will get you in trouble. > > Thanks. IMO http://meyerweb.com/eric/tools/css/reset/ should be added > to python.org regardless of PSF > redesign plans.
I advise against it in the current website state. It will likely worsen everything and you'll end up 'fixing' issues that weren't there in the first. -- Patrick Ben Koetter <patr...@python.org> Python.org Postmaster Team _______________________________________________ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
