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
If I interpret you correctly I think you are having a precedence problem. Try this:
ReplyDeletewhile (($row=mysql_fetch_assoc($query)) && ($f<4)){
=has lower precedence than&&. This means that the && operator is evaluated first.
ReplyDeleteThis means that your code, in effect, looks like this:
while ($row = (mysql_fetch_assoc($query) && $f<4)){ //this line doesn't work
So, in other words, do the MySQL query and the comparison, and if they are both true, set $row to true; otherwise, set it to false.
You need to use brackets to ensure that the right operations are done:
while (($row=mysql_fetch_assoc($query)) && ($f<4)){
That is probably because $row is true rather then the array:
ReplyDelete$ php -r 'var_dump($row = pow(2,2) && true,$row);'
bool(true)
bool(true)
$ php -r 'var_dump($row = pow(2,2) && false,$row);'
bool(false)
bool(false)
(pow being a random function here)
That is because && has a higher precedence then =. As always, solve with ():
while ( ($row = mysql_fetch_assoc($query) ) && $f<4){