Google Docs viewer gives a blank space - javascript

I'm using the Google docs viewer:
<div class="embed-r embed-responsive-a">
<iframe class="embed-responsive-it" src="https://docs.google.com/viewer?embedded=true&url=http://LINK.PDF"></iframe>
</div>
Many times, though, when I load the page, I just see a big blank space, instead of the file. You need to refresh the page one or more times in order to see it.
Any help?

I'm having exactly the same problem, but I stumbled across this whilst researching this particular issue.
https://productforums.google.com/forum/#!topic/drive/tLVhGbITFMk
It suggests that there is a 'partial sign out issue' with a Google Account. Having read the doc above and tested being signed in and signed out of my google account, it seems to have solved the problem.
It's an imperfect solution I grant, but as no definitive error code is thrown due to the security constraints of clickjacking, I get it.
It may continue to present problems to your end users, but as mine are local and limited to a maximum of 3, it isn't a huge issue to overcome with a little polite coercion.
-- FURTHER Information --
It looks like the 'solution' was a fluke and it has since been confirmed by Google that this feature is actively being discontinued. (thanks to: #omniasoft (twitter) for posing the question to Google.
Google Docs viewer returning 204 responses, no longer working, alternatives?
https://productforums.google.com/forum/#!msg/docs/hmj39HMDP1M/X6a8xJwLBQAJ
Sorry for any false hope!

Related

Why and how does firefox reveal its user is in a private mode?

I use firefox and browse a link from this website. It easily detects whether I use private mode and then it blocks me if I am in the private mode.
I searched on stackoverflow.
This answer says it is impossible. But, this website has made it possible.
Another answer suggests
var db = indexedDB.open("test");
db.onerror = function(){alert('Firefox PB enabled')};
db.onsuccess =function(){alert('Not enabled')};
And this method works fine. Although, I am not sure if the mentioned website uses the same technique.
Then, I am wondering about two questions:
1- Is this the only way to detect the private mode in firefox?
2- Why does firefox stab back its users? Is it a part of its design or is it a bug in firefox?
See this bug report. Reading that should answer you second questions. They know the problem, have tried to work on it, but clearly without success up to now. Some developers think it's stupid to make indexedDB (partially) work:
Don't expose the API if every operation is going to fail.
As for your first question. There are other methods, and most browsers seem to be susceptible. Here's an article from February '19: Google wants to make it harder for sites to detect that you’re using Chrome’s Incognito Mode.
I want to add that every website has the right to refuse visitors for whatever reason they see fit. Visiting a website is not a right, it's a privilege. Your link to the joplinglobe.com for instance, doesn't work for me because I am in Europe. This happens on a lot of sites in the USA. The reason is that they want to track users in a way that is not compatible with European law (basically: Tell people what you do, and provide or remove personal data when requested), it is easier for the sites to block access to visitors they don't care about than to spent a day thinking about the privacy of their visitors.

What does the "glGenSyncTokenCHROMIUM" error mean?

I'm debugging a WebGL application, and the following error message pops up in my console, right after a call to compileShader() and getShaderInfoLog():
GL_INVALID_OPERATION : glGenSyncTokenCHROMIUM: fence sync must be flushed before generating sync token
I've searched teh interwebs for glGenSyncTokenCHROMIUM, with no avail.
(This error seems to be hardware-specific, as I can only reproduce it on a GT-I9505 when running Chrome)
What does this error mean, and/or how can I get more detailed information of what's going on?
It seems to be indeed device/GPU/driver problem. There's bug in Chromium bug tracker (by the way, you can provide your case to it).
There're several ways to get information and help on WebGL bugs. Besides StackOverflow, there is WebGL google group (browser developers also active in it). Bugtrackers may be helpful (you always can and should report bugs to developers). And, if you feel like it, Chrome and Firefox have excellent code search engines (ff, cr), more than once I've found answers to my questions there.

jQuery v2 showing as potentially suspicious

We have had an alert in Google webmaster tools saying there was a malware issue on our site, however it didn't provide any example urls and has since been reviewed and cleared. Trying to do some digging as to why this occurred using an online scanner (http://scanner.pcrisk.com/) it has flagged jquery-2.1.4.min.js as being potentially suspicious.
The details I got from the scanner were as follows:
/styleassets/javascript/jquery-2.1.4.min.js
Reason:
Detected potentially suspicious content.
Details:
Detected potentially suspicious initialization of function pointer to JavaScript
method eval <code> = eval; <code/>
I can't be sure if this was causing the issue but want to try and find out more. I've had a search and haven't found anything directly related to why it would be flagged.
Does any know if this is an issue or has anyone found similar with a version of jQuery?

Users and Google's cache get BAD redirect

I posted a link to an excellent article on javascript deletion issues here:
Is the garbage collector called after window.location redirection?
The link is:
http://perfectionkills.com/understanding-delete/
And I can open that link just fine. It's a great article.
However, other users say it had viagra, etc. ads instead.
When I tried typing this into google:
cache:http://perfectionkills.com/understanding-delete/
I got the very same thing they did - the page was retitled "canadian pharmacy viagra", and much of the page was chopped apart (you can tell where the text used to be)
It seems the link was previously hacked somehow.
Bill the Lizard deleted the post, which I agree with - the issue made it more about the link and less about the content.
My question is this:
How can I modify the link so that it can't redirect to the old/hacked page for some people?
I think I'm out of my league with this one. Any help is appreciated.
EDIT:
As mentioned in the comments, I sent a request to Google to have the old page removed from the cache. However, I'm not certain that will be a permanent fix.
The users that were finding the bad page weren't looking at Google's cache page - not that I know of. I just tried that to see if I could see what they did - and succeeded.
I would imagine they and the cache were being redirected - so even if the cache is fixed, it might still happen to someone. Is this right?
I've seen the same results in both Chrome and Firefox, on Ubuntu 12.04 and Windows 8.0.
There might be several reason reasons why only a subset of people might be seeing the cached/hacked version:
Perhaps an edge caching server like Akamai could be serving that cached page
Google's indexes could be slowly updating (since they have multiple indexes organized by region)
The ISP could have its own cache (however, I think this one is unlikely)
The engine supplying the ads on that page (or another plugin) could be corrupt where it ends up replacing the content or downloading additional content.
The only way to tell would be to look at the Chrome Debugger. Your best bet for now is to ask google to remove the cached page here

How to integrate waze data with my web page?

Waze is an application, which offers an actual traffic information. There is also a livemap Waze livemap - where are marks as you can see.
So, I found some site: Check this link - egaraz and I'm really curious how did egaraz.cz fetch (parse) data (marks) from Waze, because there is no chance to do that. Or do they have some kind of deal? I don't know.
I tried to download all mentioned webpages to my computer, I read all javascript files and everything and found just nothing. Maybe I overlooked some...
Can you just help me and (try to) say me how do they did that? Or suggest some working solution/s..
I did some investigation on this and found some curious stuff...
It seems it's sort of hidden but there's a Waze Wiki, here's your answer:
API - use waze maps on your website
For further information please contact bizdev#waze.com
http://www.waze.com/wiki/index.php/API_-_use_waze_maps_on_your_website
(so maybe you gotta pay for it, anyhow, they're probably interested in knowing what you wanna do beforehand)
Now the interesting part is that Waze source was actually open ( seems it's not the last version tho )
https://github.com/mkoloberdin/waze
,
http://www.waze.com/wiki/index.php/Source_code (edit: link is down)
And a guy even did a Linux backport( didn't see if it works yet )
https://github.com/sashakh/waze
Edit: Theoretically it could be possible to hack an integration but this is old stuff, Waze stopped releasing the source since v3.0 and it's possible that they've probably added additional barriers to the data(I've actually ran the linux port after making this post and it seemed to work, that was the farthest I went tho)
open-source project that wrapper waze functionality
its written in java. can be used as a service or as a runnable server.
https://github.com/Nimrod007/waze-api
link to docs:
http://htmlpreview.github.io/?https://github.com/Nimrod007/waze-api/blob/master/docs.html
it has an endpoint for traffic information according to given coordinates.

Categories