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
Its nice to have such a bug list.
ReplyDeleteA simple Google code project with only an issue tracker would be sufficient to track the known issues.
If you find sometime then you can start one and share the link with all so that we can add known issues.
AndroidFragmentation.com was created last year, but I haven't heard anything about it since.
ReplyDeleteLooking at it just now, they have several hundred device specs on hand, submitted by users of their app, but I didn't notice from a quick look any meaningful way to examine or analyse trends for particular devices.