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
This message comes from the pear package of APC. If you set it, APC will be configured with the --enable-apc-debug flag, which means the macro __DEBUG_APC__ is set in the C source code.
ReplyDeleteThis macro will add additional printfs about APC's internal state. Naturally, these are only useful in a testing environment, and should never be activated on a public webserver.
Unless you're editing APC's source code, or tracking down an extremely low-level problem in APC (which is unlikely), you should answer no. You can just hit Enter.