View Single Post
Old 12-14-2014, 09:47 AM   #28
arspr
Dead account. Bye
arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.arspr ought to be getting tired of karma fortunes by now.
 
Posts: 587
Karma: 668244
Join Date: Mar 2011
Device: none
Well I can fully confirm the issue in kepubs/ACCESS. I'm updating Jellby's test book with some extra tests about it.

Quote:
Originally Posted by murg View Post
The css has no idea how large the screen is. Yeah, I know we all think that being a device, it would know how big the screen is.

In the real world, the font gets displayed in an approximate height. Many, many factors can affect the sizing.
You are answering yourself. I could admit that a general Firefox, IE or Chrome didn't know the screen size they are attached to. But here you have an unique device so, yes, you should know its size both in pixels and in length units. If you are not accurate is because you are a lazy coder...

But nevertheless supposing that the screen size is not known because of I don't know which reason, px, pt, in or cm are still absolute measure units. So if you change their chosen layout (whichever you've selected) with the internal font size setting, you're doing it wrong... (unless you do it because of a user selected option).

Last edited by arspr; 12-14-2014 at 09:50 AM.
arspr is offline   Reply With Quote