I am using Google Doc Viewer to display local PDFs on our site (override for IE7 and 8 because of permissions issue): http://www.scad.edu/news/index.cfm?pageid=338423. The issue is that sometimes people have experienced the PDF not being displayed, being replaced with an iframed Google sign in page. I am having a lot of difficulty reproducing these results, trying several browsers, even clearing my entire browser cache, using off-site browsers such as Adobe BrowserLabs and BrowserShots, etc. I know the error is occurring on an OS X 10.5 machine running Firefox 3.5.2 and on another machine with similar software. The not-so-technical personnel are claiming it happens after not having signed into Google for a week or so, but it displays fine for me when I am signed out on a fresh install. And yes, I have witnessed the issue several times on their machines but simply can not reproduce it.
Please advise on how to hunt down this bug. I can't find anyone else with the same issue. I am considering just switching to Scribd PDF viewer.
The not-so-technical personal may actually be on to something. This issue seems to occur when a Google user's session expires. The user is presented with the login form instead of the document, even when the viewer is embedded in an iframe. Apparently it's still an unresolved bug. Check out this question for more details:
Embedded Google Docs PDF viewer displays login page rather than PDF
I hope they fix this :)
this is related with permissions check your permissions and try again,i think viewer can reach your files if you give permission.
Just do this prior to loading the gdocs viewer, it should solve the problem every time.
<iframe id="google-signout"
src="https://www.google.com/accounts/Logout"
style="width: 943px; height: 1px; display: none;"
frameborder="0"></iframe>
Related
I have a site that uses web fonts.The site used to function properly until the client's IT team rolled out Windows 10 Pro across the organization. After the Windows upgrade, the web fonts stopped working with error "CSS3111: #font-face encountered unknown error" on IE 11 browser. However on all other major browsers including new Edge the site works without any issues.
I did some search to and came to know it is because of a recommended features called Untrusted Font Blocking and to disable it I need to modify certain registry keys. However in my case that is not an option as the this feature is recommended by Microsoft for security. Also it needs the change to be done on local machines.
While googling, I noticed some people suggesting encoding and embeding of font file as Base64 encoded string. In fact I could see that as a workaround in many Q&A sites and forums (eg here, here). But I failed when I attempted to do that. On my Win10+IE11 I still get CSS3111: #font-face encountered unknown error (screenshot)
Further googling led me to this SO question that actually answers to my problem. It says even if I convert the font file to Base64 the Win10+IE11 will still prevent it while converting and loading into the memory for execution.
Interestingly I found major Font and icon vendors are not attempting to figure out a workaround for this as I can see none of their website shows up properly on Win10+IE11. Even Microsoft's own site (outlook.office.com) has this issue.
Now my questions are:
Is there any workaround that can help me to fix the issue
If no workaround then is it a good idea to have a end user warning popup to switch to more supported browser with user agent detection?
Thanks in advance.
Okay, here are the facts regarding our problem:
The web site we are working on is designed to use modern HTML5 features. This includes indexedDb.
We are using the following HTML right at the top of each page:
<!DOCTYPE html><html><head><meta http-equiv="X-UA-Compatible" content="IE=Edge"/>
All our users are using the same version of IE11.
We have 200+ active users who use the site, and for most of them, everything works just fine. The browser stays in "Edge" mode.
So far though, 3 of those users' browsers started opening the pages on the site in Compatibility View Mode instead of the default Edge mode. It was working for them fine previously.
If any other user goes to any page that those 3 users went to, they open fine (in Edge mode).
I created a super-simple diagnostic page devoid of CSS, HTML5 features, etc., when the users who are having the problems go to this page, it STILL going into compatibility view mode! It seems once the damage has been done, the browser wants to go into compatibility view mode for that domain regardless of the page content!
We've tried deleting Browsing History in the user's browser including cookies and website data... it does not fix the problem.
Restarting the PC does not work.
We do not have enough security to access any registry settings or directories where the browser stores its files.
So for starters, the question is, what steps can we take to figure out WHY their browsers when into compatibility mode in the first place. The only things I'm finding are vague error messages in the F12 console about using some feature or other improperly. No info about what feature or what error it caused.
And then, if that can be resolved, for users already in this mess, is there any viable steps we can take to get them so they see the site in Edge mode once again.
I'll be grateful for any help I can get on this. I am really stumped on this one!
The organization I work for has deployed the Opera web browser to many (Windows) workstations; each is using the kiosk mode. At one time, there was a very detailed help page for this feature. However, I can no longer find it. Rather, this link:
http://www.opera.com/support/mastering/kiosk/
...simply takes me to the main Opera help page...
http://www.opera.com/help
Has Opera stopped supporting this feature? Or, are they simply retooling their help documentation?
12.14 still supports the kiosk mode. During a transition to a new publishing system recently, this link seems to have been dropped. Documentation has been notified and will fix the link. In the mean time, this should work: http://web.archive.org/web/20130223014915/http://www.opera.com/support/mastering/kiosk/
When I visit the Spotify Play Button demo page (https://developer.spotify.com/technologies/spotify-play-button/) in Opera 11.62, clicking on the Play Button gives me the (mostly-expected) popup:
The application "Spotify" must be launched to open the link:
spotify:
Do you want to proceed?
If I click yes, the Spotify app then launches (if not already running) and gets focus, but does not play anything. I suspect the link is getting broken by Opera somehow (notice that it has the spotify: protocol name but nothing after that). The Play Button on my own site produces the same behavior. Works fine in Firefox on the same machine.
Has anyone else experienced this?
Yes, sadly, that's the case. There's a similar issue in Opera's bug tracker.
I think your particular issue could be related to Opera's lack of support for cross-origin resource sharing (CORS). CORS support is coming is available in Opera Next, but not Opera 11.62. If it doesn't work in Next, I encourage you to file a bug report.
We have been facing a weird problem with PDF documents displayed in Safari. This problem is reproducible in many of our machines. The problem is like this..
Adobe Reader has support for hit highlighting in PDF documents when it is being viewed in any browser. For example,
http://www.mysite.com/myfile.pdf#xml=http://www.somesite.com/words.txt
This URL should highlight the words specified in words.txt file. But, unfortunately many of our Safari browsers (on Windows machines) don't highlight any text in opened pdf file. The same URL works fine in rest of the browsers (IE, Firefox and Chrome). I could not figure out where the problem is!
Can anybody please help me on this?
Thanks in advance,
Safari uses a built-in PDF plugin exclusive to safari (even on iPhone)
This is different from the Adobe's plugin and the API is different too.
Most of the things that work with the Adobe plugin won't work with the one inside Safari.
you may be able to find information about forcing Safari to use the Adobe Reader plugin (Google is your friend) but that would be a per user setting, something you cannot control on everybody's machine.
I'm also looking for help on this to control pdf files inside safari using javascript.