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
Check if the class exists:
ReplyDeleteif (class_exists('PDO'))
The proper way of determining that will be using the extension_loaded function:-
ReplyDeleteif ( extension_loaded('pdo') ) {
.......
}
And you might also want to check for the database-specific PDO driver using:-
if ( extension_loaded('pdo_<database type here>') ) {
.......
}
You have two options:
ReplyDeleteif (extension_loaded('pdo')) { /* ... */ }
Or (this one is not 100% reliable since it can be implemented in user-land classes):
if (class_exists('PDO', false)) { /* ... */ }
Personally, I prefer the first option.
How about
ReplyDeleteif (in_array('pdo', get_loaded_extensions())) {
... pdo is there ...
}
if (!defined('PDO::ATTR_DRIVER_NAME')) {
ReplyDeleteecho 'PDO unavailable';
}
elseif (defined('PDO::ATTR_DRIVER_NAME')) {
echo 'PDO available';
}
I hope this works