The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
Use dp for anything but for fonts. For fonts use sp.
ReplyDeletePretty much everything about this and how to achieve the best support for multiple screens with different sizes and density is very well documented here:
Supporting Multiple Screens
If you are any serious about developing an android app for more than one type of device, you should have read the above at least once. In addition to that it is always a good thing to know the actual number of active devices that have a particular screen configuration.
Screen Sizes and Densities
For some screenshots on different devices showing the differences between each unit (as well as some curious discrepancies against the documentation), see this related question:
ReplyDeleteDifference between android dimension: pt and dp
Example at http://blog.edwinevans.me/?p=131
ReplyDeleteThis might help
ReplyDeleteAfter you demystify the differences. This calculator http://coh.io/adpi/ will make your life easier :)
ReplyDelete