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
Update at the end of 2011:
ReplyDeleteFB.api('/me/permissions', function (response) {
console.log(response);
} );
console output:
{
data: [
{
create_note: 1,
installed: 1,
photo_upload: 1,
publish_stream: 1,
share_item: 1,
status_update: 1,
video_upload: 1,
}
]
}
this solution is deprecated at the end of 2011, please use the answer that is marked as accepted above
ReplyDeletefound a solution myself
function check_ext_perm(session,callback) {
var query = FB.Data.query('select publish_stream,read_stream from permissions where uid={0}', session["uid"]);
query.wait(function(rows) {
if(rows[0].publish_stream == 1 && rows[0].read_stream == 1) {
callback(true);
} else {
callback(false);
}
});
};
this will check for publish_streamand read_stream
example use:
check_ext_perm(response.session, function(isworking) {
if(isworking) {
// post something to wall
} else {
// ask for login
}
});
Generalized choise's function,
ReplyDeletefunction check_permissions (permissions, uid, cb) {
FB.Data
.query('select {0} from permissions where uid={1}', permissions, uid)
.wait(function (res) {
if (!res || res.length < 1) return cb(false);
var row = res[0];
var aperm = permissions.split(',');
for (var i = 0; i < aperm.length; i++) {
if (row[aperm[i]] != 1) return cb(false);
}
return cb(true);
});
}
Calls the callback with true if the user has all of the permissions, otherwise calls the callback with false.
The responses here that use FB.Data.query are to be avoided as this point, as Facebook has deprecated FB.Data.query entirely. The FB.api(/me/permissions ...) solution seems best.
ReplyDeleteFB.ui({
ReplyDeletemethod: 'permissions.request',
perms: 'user_website',
display: 'popup'
},function(response) {
alert(response.toSource());
if (response && response.perms) {
alert('Permissions granted: '+response.perms);
} else if (!response.perms){
alert('User did not authorize permission(s).');
}
});