I'm guessing, but I see 2 potential problems there: On 3 Mar 2010 at 20:42, Rolf Huehne wrote:
> Let's assume an initial size of 600x600 pixel. Then the browser zoom > setting is changed to 130%. Now the applet is 780x780 pixel. But CSS > will still report 600x600 pixel. Have you checked that? > But when I use this factor to calculate a new CSS setting If CSS was reporting 600px before despite the fact that it is 780px, then I think you cannot set a new size reliably using CSS. > result in the desired size of 600x600 I will get a rounding problem: > 600 / 1.3 = ~461.54 > So I would have to set the new CSS size either to 461 or 462. I bet that CSS will do the rounding for you always. This discussion is just one more reason to add to why I don't like this new behaviour of zooming all the content in the page. As far as I know IE introduced it first, so I quickly disabled it (as a user), then I was angry when Firefox followed trend (after all, we use Ff because we prefer its ways to IE's, don't we?). It breaks all fluid pages, it is just designed for fixed-pixel-sixe designs, which I think are bad. I'm probably alone in this opinion, since so many people do their designs in absolute pixels instead of relative, fluid units. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
