Images are not loading in Microsoft Edge but do load correctly in Chrome, Firefox, Safari, and Internet Explorer. Specifically, the only images that do not load are graphics hosted by the domain my computer is joined even though the images are fully qualified (ex. images are hosted at https://www.auburn.edu/...jpg and my computer is joined to the auburn.edu domain)
Using Edge's console I get the following error for each graphic: SEC 7117 - This internet explorer instance does not have the following capabilities: privateNetworkClientServer.
Suspecting it was a cross-domain issue, I opened the directory of images on the host to . (< IfModule mod_headers.c> Header set Access-Control-Allow-Origin "" < /IfModule>)
I know the correct solutions is "don't use Edge" but I cannot control that one.
Any changes I should make to the hosting server infrastructure or the HTML code? I can't force updates to the Edge browser itself although it is set to factory defaults.
(11/5 # 4pm) Update: Even more odd, this issue only occurs while on the auburn network.
Ebay Images Not Displaying in Edge, Windows 10
The Fix – In Edge Browser open settings, select Privacy, Search, and Services – Under Clear Browsing Date Now select Choose what to clear – check - browsing history, download history, cookies and other site data, cached images then click the tab “clear now”.
Goto edge browser, open ebay and start surfing.
Internet Explorer compatibility: I changed the settings to allow Internet Explorer to open compatable sites instead of Edge. Now photos are opening. I dont know enough about computers to know why, but it works for now.
Related
As I am a web-developer my work reley on web browsers .
I edited html and css files to get the exact result I want in the web design but from very starting chrome loads from its chache memory , You know chromium also do the same thing . It become very difficult for me check each time I have to change the URL in order to reload the web page to check the changes I have made on the page. While on the firefox and edge its all great up to time , please tell me the solution how can I remove this setting of loading from chache in chrome ,
I use windows 7 and 10 on my laptop
currently using chrome -Version 57.0.2987.133
You can disable chrome caching :
check out this :
Disabling Chrome cache for website development
or you can install Clear Cash extension from google chrome extensions
The Chrome DevTools can disable the cache.
F12 or Right-click and Inspect Element to open the DevTools. Now click Network in the toolbar. Finally, check the Disable cache checkbox at the top.
I can't open non secure sites (any direction with hhtp://) . Only works in https sites.
I Tried the following with no results except in safe mode.
-Diferent browsers (Safari, Chrome, Firefox).
-Deleting Preferences and system configuration.
-Reboot in safe mode (Thats Works!!).
-Checking the proxies configuration (i haven't proxies)
-Changing the DNS.
-Turning off/on wifi.
-Repair directory permissions.
-Flushing DNS Cache.
-Reseting Router.
Anyone that can help me?. I am little desperate.
Thks in advance
Finally i solved the problem and it was very very strange.
I found the following " com.erythropoieic.net - preferences.plist " file under the "Library / LaunchDaemons / " folder. This file called this script " change_net_settings.sh " changing the network Properties. I removed that files and thew problem was solved.
I faced the same with all browsers on my macbook pro. This is a malware issue. Please run anti- malware clean up using the malwarebytes.
This is a frequent problem when updating Microsoft OS or Internet Explorer. Seems the update flips the LAN Connection setting, so:
Start Internet Explorer
Click on Setting (upper right)
Click the Tools button
Click on Internet Options
Click on Connections tab
Click on LAN settings
UNCHECK Proxy Server for your LAN
Select OKAY
Validate you can now get to websites without having to manually enter https://
I had the same issue in FireFox (45.X ESR) from Linux. I could only browse to sites if I used https://. If I used http:// or www:// I got redirected to dnssearch.com (my ISP is Time Warner). It turn's my issue was with how Firefox was configured to connect to the Internet. To resolve this issue in Firefox, click the open menu icon and select Options (or Preferences in older versions) and then select Advanced. On the Advanced page, click the Network tab. On the Network page, click Settings (For how Firefox connects to the internet). Under Configure Proxies to Access the internet, there a several radio buttons. In my case, the Manual proxy configuration was checked. I changed this and check: No proxy. This resolved my issue. I could then access any site as normal.
I'm using WP Mobile Detector with W3 Total Cache and a responsive layout (media queries), and I have a few issues:
When I view the site locally (localhost) on a Blackberry, it looks good; the zoom/viewport is correct, media queries have trigger correctly etc. However, when I view the live site on the Blackberry, the viewport has zoomed out. In the context of a responsive layout, locally I see two columns, but on live I see all six columns (i.e. the Blackberry thinks it is a full browser - quite annoying!).
I thought I would deactivate W3 Total Cache to see if that was having any effect: yes, it was. When the cache is off, the viewport/zoom is good and all is well. Problem solved? Not quite...
With the cache off, I navigate to the live site and while the sub-pages of the site - e.g. www.SITE.com/about, www.SITE.com/contact - are responding with the mobile theme, when I click a link back to home (or type it into the address bar) - i.e. www.SITE.com/ - I'm no longer delivered the mobile theme, just the normal 'desktop' theme. If I go back to a sub-page I see the mobile theme again. What's going on there then.
When viewed on the Blackberry (for example), if I click the 'View Full Site' link (which triggers a Javascript function to modify the cookie) it doesn't show the full site (i.e. normal theme), it just refreshes and shows the mobile theme. However, when viewed in Firefox on the desktop (via a User Agent Switcher) the link DOES modify the cookie and switches back to the normal desktop theme.
Thoughts/Questions
W3TC does work with WPMD (mobile theme delivers minified JS/CSS), but maybe I haven't configured something correctly. The following two links were very useful and I have implemented the changes suggested:
--- http://snipplr.com/view/47970/wp-mobile-detector--w3-total-cache-integration/
--- http://journal.code4lib.org/articles/6223
Is this a known [Blackberry HotSpot/Internet Browser] issue? I have added the requisite meta tags in the document head to indicate viewport data, and the HandheldFriendly meta data which I understand is mainly for Blackberry purposes. As I said, it looks ok with the cache switched off, excepting the home page issue.
I should say it works nicely in Firefox with the User Agent Switcher extension set to iPhone 3, and I have none of the Blackberry issues.
WPMD works by setting a cookie. This appears to be working, else I wouldn't have seen the mobile theme at all.
Does the Blackberry have a problem with the Javscript function? Not easy to tell from the phone itself - might need to drop in a JS error monitor (I was looking at one the other day).
Who'd have thought mobile dev would be so tricky!
UPDATE 1
It's a few weeks since first posting, and I will soon be following Joshua and Frederick's advice to uninstall and then reinstall the [latest version of] W3TC and I'll post my results.
I found that different browsers (both desktop and mobile) treat javascript redirect statements differently. For example:
setTimeout(function(){window.location.reload();},10)
window.location.reload();
location.reload();
The three lines above effectively perform the same action (slightly different implementations, depending on your needs), but I had varying success across browsers using each one - Chrome worked with one, Firefox another, etc.. Unfortunately, I still could not get the Blackberry browser to perform a proper automatic refresh via Javascript.
What else...so, switching between desktop and mobile using a desktop PC/browser has proven interesting. Let's say we're on the desktop version, and we switch to the mobile version of the page. We're OK so far, but then we switch back to the desktop version of the page. Still OK, but if we quickly click a link on the desktop page to go to another [desktop] page then we may find ourselves looking at the mobile version instead of the desktop version.
So, what happened there? As the page was still loading when we clicked another link, did we interrupt something? Presumably not, as the cookie would have been set and sent in the previous request from the mobile version of the page to say, e.g., "show-desktop-version = true". If we do hit F5 or the browser's 'Refresh' button (or, in fact, a link to any other page) then we do see the correct mobile or desktop version (respectively).
Another interesting thing: say we're on our mobile version (using desktop browser), and we're looking at site.com/mypage, and on the page is a link to 'View Full Site' (VFS). We click VFS once and it refreshes but we're still seeing the mobile version. So we click again - same result. So we click again, and again, and again, and again, and - oh, OK this time it switched to the full site. This cycle/process seems to occur once, and then not for a while, and then happens again.
UPDATE 2
Regarding the mobile-desktop theme switching problems, please disregard my notes in 'Update 1'. One of my switcher links (from desktop theme to mobile), e.g....
View Mobile Site
...was using the query parameter (as you can see). I had used this technique to test whether a mobile browser was preventing a proper refresh as the link pointed to the same/current URL. The switcher link should have actually looked like this,
View Mobile Site
...with just a hash to allow the link to be clickable, while allowing the Javascript function to do its magic (update cookie, reload page).
Problem resolved.
(W3TC + WPMD compatibility still an issue for me - will post updates).
I am the developer of the WP Mobile Detector.
The issues you describe are exactly what happens when the W3 Total Cache is installed. For whatever reason, sometimes it is necessary to deactivate and delete the W3 Total Cache.
Two customers that I can remember reported issues even when the W3 Total Cache was disabled. Once it was removed, it fixed the problem. They then re-uploaded W3 Total Cache, made the changes at the link you posted, and seemed to be fine.
For whatever reason these issues seem to be more prevelant with newer versions of the W3 Total Cache. I need to get with Frederick (the creator of W3 Total Cache) and make sure the plugins play nice together.
Make sure to clear your cache on the BlackBerry device as well.
Without evaluating the plugin there are some things to consider here. First W3TC attempts by default to set a cookie to properly determine which page cache to use for user agent groups for smartphones and less-smart phones; it keeps unique caches for each because of the popularity of mobile theme plugins prior to popularity of responsive web design and progressive enhancement.
The user agent groups can be disabled or used to redirect visitors to another page or theme. The next release also removes the need for the cookie when user agent groups are set. A future release will also allow cookies to be used to unique cache user requests as well.
I'm familiar with the differences in rendering web fonts in different browsers and/or OS. A couple of questions though:
I use a web font (woff) that looks like crap in Chrome but is OK in FF (on Windows 7). The other day I used my office computer from home via remote desktop. I noticed that the font now looked like crap in FF too. It looked much the same as in Chrome at the office. (I didn't test Chrome at home). I know that remote desktop reduces "the graphics" somehow, but not exactly how, and I have no idea how it could effect font rendering. When I came to the office the day after, the rendering in FF was still messed up. I guess the remote desktop session´s changes to "the graphics" was still in effect. I checked with Chrome and now rendering in that browser looks fine, like in FF before!!? So I restarted the computer to get back my usual "graphics settings" but that didn't help. Then I cleared the font cache and restarted again. Now I'm back to crappy Chrome rendering and OK FF rendering.
My questions:
What is happening with "the graphics" in general, and with font rendering in particular, when I connect with remote desktop (setting = 32-bit color depth)? My guess is that whatever changes, it gets both FF and Chrome to use another rendering method than before.
How can the effect still be there after rebooting the computer. Is the "rendering result" somehow stored in the font cache as it seems?? Seems odd.
Thanks for any advice.
Chrome cannot render TrueType fonts with correct anti-aliasing at the moment. WOFF fonts are containers for either OpenType or TrueType, in your case probably TrueType, so you get the crappy rendering. You can either serve an SVG font to Chrome (bigger file size) or use a WOFF based on OpenType.
Apart from that, many other factors influence font rendering, like having the font locally on your system or having ClearType enabled or not (which is not enabled by default through remote desktop).
See here as well.
I had the same issue and searched but found no answers.
Ultimately in my case it was a combination of remote desktop, server 2012 and browser fonts (Roboto in my case).
It was the worst in chrome, ok in firefox, perfect in ie.
The cause was the missing feature 'desktop experience' in server 2012.
To add this feature to server 2012:
Click Start, point to Administrative Tools, and then click Server Manager. In Server Manager, click Features, and then in the Server Manager details pane, under Features Summary, click Add features. In the Features list, select Desktop Experience, and then click Install.
That completely fixed the issue for me in all browsers/fonts, hope it helps someone else out there.
I'm having troubles testing a StageVideo file locally. The HTML file that contains the swf loads perfectly in Chrome & FireFox, but when I go to open it in Internet Explorer 9 nothing happens (it just shows a white screen).
I've added the permissions for the location to the 'Global Security Settings' tab of the Flash settings manager (on the Macromedia website). I've also checked in the IE9 settings to make sure that it allows GPU rendering.
Has anyone encountered anything similar or have any suggestions as to why it might be blocked in IE9?
Thanks in advance.
My gut feeling is that you don't have the latest Flash Player for IE, but do have it for Chrome/FF since they're 2 different versions. The swf probably doesn't even load up because of the Flash Player requirement.