View Single Post
Old 10-22-2013, 09:56 AM   #26
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
On KT/PW differences in element's positioning. At least KT 5.3.2.1 (and, I assume, PW with equally recent firmware) provides Pillow.dpi global variable in javascripts/pillow.js script included in most (all?) Pillow HTML pages. Absence of this variable could point to device definitely being KT (but I'm not sure).

This variable, not suprisingly, contains DPI value. First part of this article explains connection between points ("pt" value in CSS), pixels and DPI.

With using of this information, concrete margin values could be computed dynamically. BTW, KT has 167 DPI, PW has 212 DPI.
eureka is offline   Reply With Quote