After upgrading to OS X Mavericks it looks like Safari (or Chrome, or Firefox.. it seems to be a system level thing) is caching the website content. I do web development locally on my machine and when an update is pushed locally it doesn't translate to the browser when I refresh the page. Even clearing the cache through Develop > Empty Cache doesn't solve the problem. I'm on OS X Mavericks running MAMP.. any suggestions? I can't seem to find any help on Google either (just flooded with Mavericks reviews).
If you're using Mamp read this. Need to comment out some lines and then it works.
http://forum.mamp.info/viewtopic.php?f=2&t=88120
Related
My ruby on rails website does not load on safari 15. It works fine on older versions as well as other browsers. The below is what I see in Safari 15
There is nothing in the console logs or any indication of what the "problem" is. Interestingly this is also an issue for my site if I run it locally on localhost:3000 which leads me to think it's an issue with something in my sites code.
If I disable Javascript the site will then load, what in my Javascript could cause this?
I have a similiar problem with my matured React app. Some users of my web application are using Safari 15 and they report that some fragments of the application are not loaded.
I also got screenshots from them. There is nothing indicated in the console.
But interesstingly all the HTML canvas elements are not rendered. Even the small ones.
Some examples:
Leaflet map in canvas (map tiles somehow not rendered):
A chart in a canvas (chart stays blank):
I mean it is working in every other browser since years and also Safari 14 and Safari on iOs.
Must be something Safari 15 realted.
For me this ended up being an issue with Three.js, I needed to upgrade it's version then the site worked in safari. If you're not using Three.js, then I'd recommend checking the other JavaScript packages you are using.
When using chrome dev tools to emulate mobile devices, sometimes when toggling emulation from mobile back to desktop the user agent spoofing gets stuck in mobile. I've tried hard cache reset, closing browser completely, restore to default.... but anything I do the site still renders in mobile (even when emulation is turned off).
This happens in Canary, beta, and regular Chrome.
Also a note i've only seen this happen in Sharepoint.
Anyone know how to resolve? Nothing seems to get the dev tools to change user agent back to default when exiting emulation.
Have you tried deleting your chrome settings?
Windows: C:/Users/%username%/AppData/Local/Google/Chrome/User Data
Mac OSX: ~/Library/Application Support/Google/Chrome/
Ubuntu: ~/.config/chromium/
Also make sure you aren't ZOOMED! Gets ya everytime
I ran into this same problem previously when using dev tools in Chrome to look at mobile resolutions that got me permanently stuck in mobile for SharePoint only. I solved it originally with the recommendation above of deleting my Chrome settings folder, however, that meant I had to sign in again, sync my extensions, etc.
After forgetting that this would happen again, I ran into the same issue, but this time I discovered that if you append the following to your SharePoint URL it will reset this back to non-mobile. I verified that it is not temporary as I have closed my browser, reopened, visited SharePoint, and it still loads in desktop mode.
/?mobile=0
So, you would use your site url, e.g. https://siteurl/?mobile=0
Weird, this just started happening to me. It persists in new tabs and new windows. Only fix is to open DevTools and switch to Responsive mode and then pull it way out. As soon as I turn off Responsive / Mobile view, Chrome snaps right back to a mobile view by default (appears to be iPad size).
The solution for me (so far) was to quit Chrome and open it back up.
I'm currently trying to set up a connection between my web client and my iOS app, but for some reason my iOS client only sees a black box when using Chrome (version 33). I can see the video just fine if I use Firefox (both in my app and when I put the browsers side-by-side, they can see each other).
This doesn't appear to be a documented known issue with the JavaScript SDK, and I can't see any recent discussion about this on the forums (last post was mine).
The iOS sample can be located here (samples/OpenTokHelloWorld) with the browser page in samples/OpenTokHelloWorld/browser_demo.html
I suggest cd'ing into samples/OpenTokHelloWorld and running python -m SimpleHTTPServer, as it can't be run from a file:/// path.
Here is what my iPad sees:
Chrome:
Firefox:
And Chrome/Firefox (respectively), both publishing video from the same camera
Edit: after testing on other machines, it may be something specific to my environment even though none of my extensions run in Incognito and I don't have any custom plugins installed.
It looks like the OpenTok mobile SDKs with the specific webcam I was using has issues. On Android the video stream will display for a brief moment then segfault, and on iOS there will be no video at all.
I have tested this many times and could not reproduce what you are seeing in your chrome.
Without seeing any console errors or iOS logs the best suggestion is to try clearing your cache, or maybe restarting your computer (longshot)
A client's website was working fine, until they had some problems with their web host. Temporarily, the Apache CentOS Test Page was visible. The host claim the problem is fixed - and it seems to be - for everyone but me...
I'm using Safari 7 on OS X Mavericks and every single time when I visit their site I still see the test page.
When anyone else uses their own computer with any browser, it works fine...
When I use Chrome on my Mac it works fine... So the problem is just with Safari.
I've tried clearing Safari's cache
I've tried clearing the DNS cache
I've tried a restart
But I've got no idea why I can't access it. I need to access the site to work on it - yes I can use Chrome, but Safari is my primary browser. Any ideas?
It turned out this was caused by an issue in a Regex within Apache's Mod_Security. The Regex falsely identified a string contained within a cookie as being an SQL injection (it wasn't - purely coincidental).
I'm using microsoft's CDN for pulling down the Ajax libraries. And I'm using SSL on some pages.
This URL resolves fine in Firefox and IE:
https://ajax.microsoft.com/ajax/4.0/MicrosoftAjax.js
However in google chrome (on my PC, today...) it seems to time out with a very odd response:
On other PCs it seems to work fine, however I know I'm not the only one experiencing the problem as we've had occasional complaints from some of our clients about certain pages timing out and failing, that seems to point to the same problem.
As per my comment, I experienced the same issue but with Firefox failing and Chrome and IE succeeding.
Restarting the browser and the computer had no affect. Clearing the browser cache did fix the issue. I can only assume there was some kind of corruption in the browser cache.