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
Based on my experience, most users don't know what permissions are, what they mean, and just click their way to the download as fast as they can. You could ask the permission to empty their bank account and date their wives and they wouldn't read it.
ReplyDeleteOf course there are exceptions but so few.
It's against AdMob's terms of service to provide location information if the application itself does not use location. So I would recommend that you don't add the permission only to pass the location to the ad networks.
ReplyDeletePeople are going to complain about it in the comments, I would suggest explaining any permissions in the App Description field.
ReplyDelete