I have an application that contains an iframe where I load an external website.
This website uses a indexedDB database to store some values. All works fine in Chrome, Firefox... but I have discovered this error when I try to open the app with Safari:
Could somebody tell me something about what is happening with Safari?
Regards
As of now Safari does not support the usage of indexeddb when embedded in an iframe.
Apple says it is because of "security" :-(
Edit: this is only applicable to cross-origin. If the two urls are same origin the use of indexeddb works as expected.
And if you only use it internally perhaps you can: Go to Safari, enable developer tools (Preferences > Advanced) then Develop > Disable Cross-Origin Restrictions.
But this is only feasible if used internally.
The current state is a total mess.
In an iframe scenario you can only use localstorage (or sessionstorage) but that only gets you a storage for a few mb.
Or to go the old route and store everything on the server.
Related
I've been hired into a company that uses ASP.NET for all of their external and internal sites. I'm not too familiar with ASP.NET.
I'm currently working on a external site that runs perfectly in Internet Explorer.
When using the site on chrome, I have certain pages that give me the 404 - File or directory not found.
What can I do to help prevent this error code from showing up when using this site the chrome?
From your description, I understand that your site is a legacy site that is compatible with the IE browser but it is not working properly with modern browsers.
The 404 error information generally informs us that something is not found but if the site works fine in the IE browser then it could be possible that the issue is something else. In that case, this is too little information to predict the cause of the issue.
You may need to provide detailed information about which exact piece of code has the issue. Which version of the Asp.Net project and which kind of project(Web application, web API, etc.) it is. You may need to modify your code or project to make it work with modern browsers including Google Chrome.
At present, if you don't want to make any changes in your code then you could try to use the IE mode in the MS Edge browser to load your legacy site.
You could configure the IE mode manually or using the group policy.
To quickly check it, Launch the Edge browser. Paste edge://settings/defaultBrowser in the address bar and press the Enter key. Add your page to the Internet Explorer mode pages. Visit your site, it should load properly in the IE mode in the Edge browser.
I synchronized my project with a remote, but it looks different locally than when hosted online. Locally, it appears like this:
But looks like this online:
I refreshed the Chrome browser multiple times to no avail, but found that the styles showed up correctly in Incognito mode. Why?
This is most likely due to Chrome's caching of your files. Due to caching, you're seeing an old version of your styles. In incognito mode, this is not a problem because Chrome uses a fresh cache when you start a session and removes that cache when you end the session. You can solve your problem by clearing your cache.
In general, it's a good idea to test your application in incognito mode because it gives you a good idea what someone sees when they first visit a site, and it allows you to experience your application in a clean environment without any extensions or cache.
Your internet browser stores "cached" versions of your website to improve load speed. Normally this isn't a problem, but it'll often interfere with showing the new styles whenever you're doing web development.
Try clearing your cache. There are some useful Chrome browser plugins you can use for this, or you can do it in the Chrome settings.
I am building a website.
I built it locally, it works both in Chrome and in Firefox (when navigating the files locally)
I uploaded the files to amazon s3
and here's where I get some funky behavior.
if I use the amazon endpoint url to access the site:
it doesn't display properly in chrome, but it does in firefox. (what I mean by doesn't display properly is that parts of my css aren't being loaded in chrome, but they are being loaded in firefox)
if i navigate the local files on my machine:
it works just fine in both chrome and firefox. Everything is displayed perfectly fine and all of the css gets pulled in and rendered.
I guess what I'm curious about is, would behavior like this be an issue with Chrome or with Amazon AWS?
If parts of my css aren't even being pulled in by chrome (as in, when I open the developer tools, the css lines don't appear and I just get the default css associated with tags), it seems like this would be an issue with either chrome or AWS.
but when I use navigate the files locally in chrome, everything works just fine. So now I can eliminate Chrome as the culprit and point the finger at AWS.
But then when I use the aws endpoint in Firefox, it works just fine again...
So AWS isn't to blame either?
Im just curious why I'm getting different behavior based on how i choose to open the files, even though the files are the same both locally and on amason s3
UPDATE: So I sent an invalidation through cloudfront distribution.
Now when I visit the domain that I own and run the site off of, everything works both in chrome and firefox.
But the Amazon AWS Endpoint is still displaying improperly in Chrome despite the fact that the regular domain works... In the end, nothing is broken when the end user visits the site or when I edit the site locally, so it seems that the amazon endpoint is to blame.
If anyone has any ideas, now I'm just curious what the hell is happening inside of AWS
So I recently bought a theme that uses less css, I tested it on my local wamp server and everything worked fine in ie chrome and chrome mobile.
I then proceeded to upload it to my online server and everything worked fine in chrome, ie and then when I tested it on chrome mobile it didn't load the css, but if I use opera mobile on the same phone it loads fine, so clearly the fault is with the server but not sure what the problem could be,
Any suggestions, ?
Check your .htaccess file on your web server to check if there is any kind of caching enabled,
If there is you need to remove these data stores / caches so that the browser downloads the new content rather than rendering the cached (old) version of the CSS.
To do this on chrome select Chrome and the Clear Browsing Data
p.s. Its worth trying this even if you .htaccess draws a null just to be sure...
I have a Web Application (ASP.NET C# for .NET 3.5) that uses the Session object to store, amount little things the debug information so when things go wrong, this is the first place to go.
The process is simple actually,
no matter what browser (except IE), when I navigate to a page, in the Debug Log I have data, just like the one show below
alt text http://www.balexandre.com/temp/2010-04-14_1048.png
problem is that in Internet Explorer, the Debug Log is always blank (blank as no information, not no html code)
alt text http://www.balexandre.com/temp/2010-04-14_1051.png
What can I do?
I tried several Security settings of IE8:
add the site (machine name) to Trusted Sites
disable Protect Mode
set Local intranet security level to LOW
set Accept All Cookies under Privacy
checked the Allow Active Content under Advanced tab
I really don't know what more can I do :-(
Any help is greatly appreciated!
You could try using Fiddler - a web debugging proxy - to check traffic between IE and your site. Also, if you can, try other versions of IE on different machines/networks to see if it's a global problem, or just related to one browser. And don't forget you can hit F12 to enable developer console in IE.