Hello,
On Tue, January 9, 2007 00:49, Brion Vibber wrote:
...
I asked you what *you* were running so I could try to
reproduce the
problem *you* described.
Ok, so I answered and I added some remarks about OS-es.
Sounds like a bug in Firefox; ...
No, really, Firefix works just as designed and as specified.
Well, that would be a surprise; can you show me the design
specifications for Firefox's print scaling feature? :)
Ok, there is not a clear standard. But the tendency to interpret CSS more
strict was encouraged by Mozilla / Firefox, and rendering a fixed font
size _as_ a fixed font size seems like a reasonable decision in this
context.
In fact, a quick search through bugzilla shows that
this is a known bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=205001
.. 153080 .. 177805
That some people consider this to be a "bug" doesn't mean that other
people before have not thoroughly discussed this point - and decided to
code it the way it works now.
.. Scaling, by definition, would need to
change the logical resolution of those document absolute units as well.
It might make sense in some applications to have a font-size that will not
be scaled - and giving a css designer the choice makes sense as well.
(And in fact the behavior is correct when printing
from Firefox on Mac
OS X, so the bug appears limited to the printing subsystem on some other
platforms.)
The Mac OS, when I remember correctly, has its own font system that might
take the decision how to render fonts completely out of the applications
hands.
...
http://en.wikipedia.org/skins-1.5/monobook/main.css?41
.. and you fill not one font-size in 'pt', only percent, ems ..
I'm not sure what you're trying to say here. If you're trying to
convince us that the use of different units in one of our style sheets
means that there is not a bug in Firefox's printing modules on some
platforms, I don't think I'm convinced. ;)
I was trying to say that the designers of monobook.css were wise not to
use 'pt' at all.
And that this kind of wisdom should be applied to commonprint.css as well.
Just because I ask you questions about a bug I
can't reproduce on my
system without more information from you doesn't mean I'm out to get you.
Hey, we're in a mailing list - how should someone "get" someone else?
;-)
// Bernd
