So I have this slideshow in the homepage that shows five slides. It works ok, but not under https
Firefox loads great with no issues under https but not chrome nor IE9/10
What could be the problem?
Once possible problem is that there might be some syntax error in your webpage. Try running it through software like visual studio to dreamweaver to look for errors. Certain web browser can be forgiving but this is not the case for most browsers.
Related
I'm trying to load http://m.zara.com from my desktop browser. I have tried with Chrome developer tools to change the user agent to mobile. I have also installed User-Agent Switcher plugin for Chrome without any success. For some reason it is always redirecting to the desktop version.
Why is this not working? How could I manage to do this?
Checkout the link here
Try to download user-agent extension in chrome browser and then you can use the online parsers available in this blog.
There by the simulation of browsers can happen for cross browser access.
This is kind of a long shot, but I'm at my wit's end. At some point in developing a locally hosted Foundation page, the Chrome Developer tools stopped displaying the stylesheet and line for each individual CSS rule when inspected, but instead just seems to show the media query for the element. I've noticed that other pages I've built with Foundation, locally hosted are doing the same thing. It only seems to be locally hosted Foundation pages that are giving me this problem. Locally hosted Bootstrap pages work as expected, as well as Foundation pages that are actually hosted. I have no idea what is going on here, or why the Developer Tools would just stop working in the middle of a build. I've checked all my settings, went as far as downloading Chrome Canary and am seeing the same results. I'm not running any kind of local server like MAMP, and this have never been an issue in the past.
Any help?
If you are using prefixfree.min.js just remove or comment it out and everything should go back to normal.
I'm pretty sure the answer was in my file folder structure. The parent folder contained a blank " "space, replaced with a - everything seems to work.
I have a dev site for a store here where fonts are not showing properly in IE10: http://darciekentvineyards.com.uswest.vin65dev.com/Wines
They work on the live portion of the site in IE10: http://darciekentvineyards.com/about
They also work in Chrome.
I'm not sure what's causing this or why there's a scrollbar on the menu. Does anyone have a solution?
This is caused by restrictions on cross-origin use of fonts, as you can see if you press F12 in IE and select Console from the IE developer tool, then open the dev site in the browser. There are many error messages in the consolte about resource loading failing due to cross-origin request.
The simple solution is to upload the fonts onto the dev site too.
So I'm running my Rails app on a Nitrous.io server, and Chrome's web inspector is displaying some weird behavior that I've never seen before. When I try and modify some CSS in the web inspector, it automatically switches back to the previous CSS and doesn't make any live changes. I've never experienced this before and rely heavily on web inspector to work on the CSS of my site.
I'm currently running Chrome OS v29.0.1547.74 on a stable build.
I would post my css file but it's pretty long. Any idea where I should start looking to debug this? I really need to be able to make live changes in the browser to work on this site.
My CSS passes the W3C CSS Validator, all I get are warnings for 'unknown vendor prefixes'.
I've seen this post on Google's product forums, but who knows when that will be answered, so hopefully someone here may know.
On my site, the video will not display in Chrome (latest). It works fine in IE[x], FF, and Safari. In Chrome, the console shows this "warning":
[blocked] The page at https://www.mightyspring.com/ ran insecure
content from
http://www.youtube.com/v/cFxF3lWsdPE?enablejsapi=1&playerapiid=homepageVideo&version=3.
Anyone have any idea what's wrong and/or how to fix it? Or is this just a bug that will fix itself in the next release?
Just in case anyone comes across this issue, the answer is because Chrome is properly blocking the site from loading a video not behind SSL. My live site is actually https:// (see the "s"?) and I had the protocol as http://