I have been developing a website for a client this past week and he tells me the site works fine on chrome but not on safari.
Unfortunatly I do not have an apple device but the site works fine on all the browsers my end!
Here is a video showing how it looks on Safari:
https://a.uguu.se/l0yAhSOlet1C.mp4
Not sure what more I can do to it but I'm pretty sure it's not my code!
Many thanks for any suggestions.
Phillip Dews
I found that the problem is definitely not in your code, it is a know issue I quickly searched on Google and I found that there are quite a bit of people that experience this issue I think probably because they are running an older version of Mac OS.
Here are some useful links you can read and inform your client:
A lot of people have similar flickering patterns.
Link 1
Link 2
Link 3
I have just completed a new Shopify website and used mainly Mozilla Firefox to put this together. I have been told by the client that the site doesn't show up properly in Chrome and Safari but when I have checked this on my 13" laptop they both appear fine on there and I was just wondering if anyone can give me any tips on how I can ensure that the site is working on all common browsers without having any issues.
Would appreciate any tips as I know there are paid websites to do this but just wondering if there is anything else that I can do to get this fixed.
If you to the safari developers "dropdown" in the status bar the is an option called "User agent" (the second one) from there you can "change" the browser.
Disclaimer: never actually used this function.
I believe that the best way to handle this would be to download and install all browsers to test.
There is a free service from the Microsoft dev site that gives you screenshots from a couple of different browsers and versions. Here is the link -> https://developer.microsoft.com/en-us/microsoft-edge/tools/screenshots/
It's not as good as installing all browsers to fully test everything but it can give you a rough idea if there's something wrong with css or something like that.
Your issue might be related to different browser versions. Double check to make sure that you are on the same version to see if you can reproduce the issue.
I've just realised that on my website, the images look a lot different to what they do on localhost. I'm not sure why, it's baffled me.
Localhost preview: http://d.pr/i/6og
Server preview: http://d.pr/i/OWKx
Localhost gradients: http://d.pr/i/C5el
Server gradients: http://d.pr/i/5pGi
Localhost search bar: http://d.pr/i/YL2X
Server search bar: http://d.pr/i/dTCZ
As you can see they're a lot different. I've literally no idea why, I'm wondering if anybody has had the same problem before?
My website: http://wpvault.com/kahlam/
I don't think there's anything in the CSS that could possibly do this? It's strange, quite stuck with this one. Any help would be much appreciated.
Browser: Google Chrome
The problem is color management in browsers. This isn't a fault with your images at all.
Here is the article that I read.
Here is some excerpts from the article in question:
This specific issue exists because there are two types of ICC profiles, V2 and V4 (all you need to know is that V4 profiles are more accurate; refer to this International Colour Consortium document for the technical specifics).
The trouble is:
Firefox 3.0 and Safari understand ICC V2 and V4 profiles.
Firefox 3.5 introduced a new colour management system which no longer understands ICC V4 profiles (great job guys).
Internet Explorer 8 and Google Chrome don’t understand colour profiles at all!
Edit
I also found this link to blurry images in firefox, this could be related to other browsers as well.
I recently faced a weird issue with Firefox. All the images on my blog were rather blurry as if they were wrongly scaled. So I tried with a new Firefox profile and it worked fine. So there must have been some setting or some add-on that is part of the current user profile that is causing this. I removed all the extensions and add-ons to no avail. Just moments ago, I found the solution on the Blitz Research forum. It turns out to be an issue related to the zoom level for a given website, which Firefox 3.0 remembers. By clicking Ctrl + 0, you reset to the no zoom.
Very strange issue but I have all the images back to normal. It seems when I was uploading them from a 2mb connection it was just uploading them into really rubbish quality images. I got home and uploaded them via my 50mb connection and all was fine - all the images are now back to normal. Thanks for the help.
I am working in creating a website and I want to check in multiple browsers for Browser Compatibility test automatically by using Automated Test Tool. Do you guys know if there is any software/tool where I can just give a link and it loads the page in multiple browsers?
I've used Browser Shots before and it's ok if you don't mind waiting for an hour or two.
I'd also recommend checking out some of the links on Delicious.
You're looking for litmus, from the people who brought you doctype, part of the League of Justice. 14-day passes to test your layouts in 24 browsers currently cost $39.
I'm a fan of XenoCode's "Spoon Browser Sandbox" myself.
You can use Selenium RC (Selenium 1) or Selenium 2 (WebDriver) for automated test. But You have to record the test using Selenium IDE on Firefox browser and writing some tests on it. Selenium supports FF, Chrome, IE, Safari and Opera.
If the website is publicly visible then there are web based services that you can use such as http://crossbrowsertesting.com/.
If your website is internal only, then you're going to struggle to find support I think. We tried to find one but all we found were services that require a publicly visible website - no good for testing pre-go-live.
Are you talking about a compatible design or compatible JS? Because AJAX functionality is difficult to test with the usual cross-browser tools.
For the latter, look at httpUnit, though I'm not sure it can simulate multiple browsers.
There's Microsoft Expression Web SuperPreview, but I haven't tried it so can't comment on if it's good or not.
Their opening quote makes me laugh though, mainly because of how sucky IE6 is:
About 7 years ago, the browser wars
were over. Internet Explorer had
become the de facto standard, and for
a while, there were very few
compatibility issues in web page
design.
Check it out though, might be worthwhile. Especially if you are a .NET developer, however it might be useful to web developers in general.
Adobe has BrowserLab. It requires an Adobe account (free) and gives you Firefox 2.0 - 3.5 (WinXP, OSX), IE 6-8 (WinXP), Safari 3-4 (OSX) and Chrome 3.0 (WinXP).
Is anyone writing applications specifically to take advantage of google chrome?
Are there any enterprise users who are considering using it as the standard browser?
Yes, I have started to pay very good attention to Google Chrome for my applications. Recent analytics show that between 6%-15% of my users are accessing my applications (varies between 6 to 15 in different applications) on Chrome. And, this number looks on an upward trend.
Thus, I can't really ignore it for testing right now.
As far as taking it as a standard goes, thats a long way off. I still have to test for IE6! :( Though, we have been planning to start using features like Gears (inbuilt in Chrome - downloadable elsewhere) once Chrome crosses the 25% mark. Thats when I believe that we will be looking at Chrome to be our preferred browser. I hope that we have Chrome 1.0+ by then! ;)
I switched to Chrome and haven't looked back except for the occasional site which doesn't work properly, forcing me to load it in Firefox. All my existing web applications work fine on it, and I'm using it for primary testing on my current development project.
I'm not actually targeting chrome, but I have added chrome to my browsers to test sites on. I've found some odd quirks in this product where some plugins cause the browser to hang, or run really slow in some environments, but they are still in beta in active development. But I definately now make sure sites I work on render well in chrome, as well as firefox, latest versions of IE, safari, Konquerer and opera. I usually check out how it looks on lynx as well, that helps me catch "un-alternated text" in images. Yeah, I know that isn't a word, but some people will understand what I'm saying.
Because chrome uses the webkit to render HTML, you can be assured if it works in safari, it'll work under chrome, however it's rendering engine isn't up to scratch quite yet. I think writing applications that take advantage of it is similar to writing iPhone applications, remember chrome is expected to be adopted by android to make it similar to iPhone. That way it pretty much takes advantage of all those iPhone apps.
Would I install it as the browser of choice? not yet - but i'll certainly work on valid web pages that will render across all browsers.
One of our major customers has outlawed Chrome because it installs on the C drive without asking. They deploy a standard image with a small C drive and large D drive so they can easily re-clone the system part of the image on C without destroying the client's personal files on D. Most software allows you to choose the install directory. Anything that violates this is disallowed, and they're a big enough company to have some weight with most vendors.
We have enough headaches trying to support
Firefox
Two versions of IE which have their own iffy bugs
Safari
I'm not sure why we continue to support Safari. Most of our users (corporate) use IE6 or IE7. We try to make sure that things work in both of those.
Maybe not for programming purposes but Chrome w/ Google Reader makes for the most powerful RSS reader. Can handle up to 1500 feeds w/ performance still ok, managing subscriptions still functioning.
I'm using it on my work machine, but that's about it. It's been stable for me, and I like the barebones UI. I'll still switch to Firefox for the web developer extensions however.
I'm liking some of GoogleChrome- the Start page with your 9 most recent is the winner for me. The interface takes a little getting used to, but the speed is impressive, especially with Gmail.
However, it glitches with Java, which rules it out for serious work at the moment. I use FireFox mostly and have Chrome for the "other" websites at work.
I'm considering using GWT on an intranet project and considering suggesting to the users that use Chrome to take advantage of the enhanced Javascript performance. Any AJAX-heavy app would be a great candidate to target Chrome.
At my company, we're not targeting it, but we're definitely paying attention to it. My boss is using it as his primary browser, and I have implemented browser detection for it in our scripts in case we ever to need to target it for some reason.
Chrome has the .png opacity bug where the transparent parts of the .png are a solid color if you try to transition the opacity from 0 to 1. In IE7 the opaque parts are black, and in Chrome, they are white. Today, I decided to go ahead and account for this bug in my JavaScript. I don't really test sites on Chrome that often, but I am actually using it for almost all of my browsing.
I will target Chrome as soon as a stable Linux and OSX client is available.
Targeting Chrome/Chromium right now, I think is like targeting Konqueror web browser. It will get popular, but you should wait to a more stable beta, and/or some Linux and OS X client.
My website statistics shows 3.xx % visitors using Chrome which arrived just few weeks back. And Opera is only 4.xx % which has been around for several years.
Easily you can see that rate at which Chrome is picking up.
You can see how easily Google takes over all areas of your computing world and personal world too.
Since Chrome uses Webkit, it has the same rendering engine and DOM support as Safari (not necessarily the same revision of Webkit though). By testing in Safari, you can generally get by without worrying about Chrome. Any differences you find are probably just bugs that you should file on instead of work around.
However, because Chrome uses a different JS engine, there may be a few incompatibilities with Safari. So, if you're doing anything with JS, you might as well fire up Chrome and see if there's anything obviously wrong.
Generally though, you don't target browsers, you target rendering engines (with their associated DOM support and JS engines).
I am using Google Chrome, so far all the web apps I have work fine in it with no modifications.
No.
Why help Google further build an evil empire? In this particular case it is so obvious that they do not care about users but only obsessed with gathering usage info.
It's not any major player yet