I have a php facebook application that requires that you like the page before getting access to photos Free Cover Photos. The problem is after liking it not all browsers take you to the application. It requires you to refresh the browser to view. Any suggestions?
IE worked ok
FF needing refresh
Chrome needing refresh
Tested on several systems.
It looks like Chrome is working for me. Maybe you have an older version of Chrome or some non-default setting turned on. Try turning off all the plugins in Chrome and see it that helps...maybe one of them is getting in the way.
Related
I have been working on a simple portfolio for myself and have it deployed to an app on heroku. I have used the typical commands to add, commit, and push to GitHub and everything is updating normally there.
My issue is that when I open the app from Heroku in Chrome, it is not displaying the recent updates. When I open the link on my phone, it looks correct according to my HTML and CSS code. I have tried both automatic and manual deploy methods, but I still cannot get Chrome to display any of my updates.
Has anybody experienced this? I'm including screenshots below.
How it displays in Chrome
How it displays in Mobile Safari
Chrome sometime uses previously cache data of website to load website faster unlike safari, try using incognito mode or another pc or even a smartphone. There is also a service called browserling where you can test out on different browsers.
Just to be on the safe side before starting to code: Are there any problems with embedding activeX in FB app?
10xs,
Nahum
Your FB app won't work on any browser except IE (I think there might be extensions for other browsers that might let you run ActiveX controls). If you're okay with that limitation, it should work, since it will be running as an iframe.
I have a fairly standard ASP.Net web application which is used via mobile safari on the iPhone.
Some users who have a link to the web application placed on their desktop via profile are reporting that when navigating between pages (which I do on the server with Response.Redirect after specific events or via standard anchor tags in other cases (no target specified)) that Safari opens a new window instead of reusing the existing window.
Because of this, any login token/cookie etc (i'm using the built-in ASP.Net membership stuff), is now gone for that new browser window and the login prompt is shown.
The problem doesn't happen every time, and I can't seem to replicate it on my device (but i'm not deploying the shortcut via profile)
As you can probably imagine, it's quite frustrating for the users to have to log in every time, and you can't fix an issue you can't replicate.
My question is, has anyone heard of this issue and/or know a workaround?
The app is NOT iPhone specific, that is, it is used in a full desktop browser as well, and the logins stay like you'd expect there - and the same window is reused repeatedly.
I've considered a few possibilities, but have been drawing a blank as far as what might be causing this or how I can resolve it.
Do you have any iPhone meta tags set (to remove the url bar or the toolbar, for instance?) If you do, the phone will assume it's a native web app, and urls will open in a new safari window, like they would for any other native app.
If you are taking advantage of using the web app in full screen mode (where it is bookmarked to the launch screen next to native apps) you can prevent it from jumping out of fullscreen mode by and in to safari replacing type links with javascript.
location.href = '/yourPath';
This is a nifty trick which even works if you are linking to an outside URL, like doing an OAuth to Facebook and back.
I have a blog post on this here: http://www.aaroncoleman.net/post/2011/07/29/Keeping-iPhone-Web-App-in-Fullscreen-mode-from-Homescreen-Launcher.aspx
I'm playing around with a simple web app locally, and can't quite figure out why it is not caching correctly on the iPhone. I am serving a .manifest file with the correct MIME-type, and the site works perfectly fine with my local server turned on or off on desktop Safari, Chrome and Firefox. It is only mobile Safari that is failing to cache the site. Any ideas why this might be?
It seems to be an iOS bug.
I found out that mobile safari will always run into an application caching error if you have at least one web view opened and the you clear the browser cache. I think that clearing the browser cache will destroy the cache database. All accesses to the cache database will then fail. It seems that the browser creates this database only on startup.
To get the application cache working again close all safari views and finally close the browser by returning to the home screen. Now applicaton caching should working. Some mobile devices also requires switching on and off.
If you know a methode to detect this situation let me know it, please.
I had a similar issue but Safari and iPhone were both NOT working whilst IE and Firefox were working. The reason was complex. One was a misspelling of the word "manifest" in the HTML tag. Silly mistake and very frustrating that IE and FF still worked offline. The other issue was that I was using default.asp as the main page of my app and not including this in the manifest.
My app was mydomain.com/myapp/ and thus the browser never saw the "default.asp". Also, according to the HTML5 spec, the main page need not be in the manifest but apparently Safari sees that a little differently...
I can confirm that the bug is also present on iPAD running iOS 4.3.
I spent quite some time to make the offline application cache work on iPad. I can confirm that the workaround mentioned in the previous post works.
I am using GWT-JAVA. The Login page displayed good in firefox.
But In IE It is too slow and also Fonts are too big.
In chrome it display only the background image. Nothing will be display.
Is it GWT a browser dependent? Otherwise Can i change any other options or anything else?
Thanks in advance.
GWT is intended to be browser independent, but there are limits. Are you following the advice in the "Cross-Browser Support" page?
Speed of old versions of IE will always be an issue for any browser-based UI toolkit that relies heavily on Javascript.