I'm making an old website with HTML. I used the reset.css and I can see this perfectly on the web (http://www.ceachile.cl/revista/) with Chrome, Firefox and IE10, but my client can't see some elements properly. I don't know what else can I do to fix this table that is in a wrong place. Here's a folder with a lot of screenshots of the site in many browsers and OS.
Some snapshots of what the website looks like under various browsers can be found here
You have to check with elements of HTML and CSS each of the browsers support. Trident has historically been behind in implementing a lot of newer features. If you aim to support older browser, you have to look at their documentation and write code based on what they can handle.
Take a look at http://msdn.microsoft.com/en-us/library/bb250496(v=vs.85).aspx for ie7.
If you know your client's OS and browser version, you can use a service like www.browserstack.com to test your website in this environment and debug it with the usual developer tools.
Recently users of my website complained about the lack of support to IE6\7.
Is there an offline tool to test if a page-HTML isn't compatible with a specif browser and where is the problem?
Where can I find a list of things I need to be aware of in order to support IE6?
Update: The problems the users describe are in the UI, <Div>are not in the right places and that kind of problems, not JavaScript issues.
I can't force the users to upgrade theirs browsers.
IE6 is an ancient browser. Tell people who complain about lack of support that it's no longer supported and they should upgrade.
There is no "syntax checking" tool to find all incompatibilities, because the problems are not in syntax but how it's interpreted. There is no way around visual testing I'm afraid.
Here are some interesting SO questions on the topic:
One fix for all IE6 problems
How are programmers tackling ie6 bugs these days?
Running Internet Explorer 6, Internet Explorer 7, and Internet Explorer 8 on the same machine
IE tester is useful for testing across version of internet explorer. It may not tell you what is wrong but you will at least be able to see / verify what users are reporting.
http://www.my-debugbar.com/wiki/IETester/HomePage
I have some offer about this for you :
Try to use Jquery more,because Jquery is compatible with most browsers
there are 3 useful addons for Mozilla : Firebug , Web Developer , IE tab
IE 9 has a developer windows that you can change your page standard into IE 8 or 7
Use syntax liek this :
<link rel="stylesheet" type="text/css" href="Styles/ie-fix.css" />
maybe this is useful dude for you :)
If your users are complaining about IE6, you should give support to IE, thats theory. BUT, if possible do as google has been doing for years, if the user is using IE6/7 or lower show some links to download newer browsers and tell them that their browser is too old.
You can use a seperate stylesheet for IE.
There is a third party software named Utilu. Utilu IE Collection contains multiple standalone versions of the browser Internet Explorer, which can be used at the same time. It has more than 10 versions of IE. But its used for viewing the web pages. This software also has firefox and chrome collections.
I'll try to be short and clean. I did website for friend, although she says some people complain about pink quote field to cover the text area, I've tried this on different PCs, browsers but haven't seen this kind of issue. So I was thinking maybe that old IE or something?
Here's websites link: http://www.zlobekbambino.pl
Thanks in advance
I would try using a service such as Adobe's Browser Lab or Browser Shots to test the site in various browsers to see which is causing problems. You can then try to work out how to fix it.
Assuming you have a Windows PC, you can test with all versions of IE by installing IETester. It's a very usefull program that allows you to run all versions of IE in tabs in the same window.
Obviously though, it only works on a Windows PC, so if you're on a Mac you won't be able to use it. In that case, http://www.browsershots.org allows you to download screenshots from virtually any browser ever released. The downside of that is that you only get a static screenshot, so not much use for testing dynamic content, but still a useful tool.
I have a website that I'd like to monitor for display problems in various browsers (mainly Internet Explorer.) I know that browsercam.com and broswershots.org provide this as a service. Could anyone recommend the best way/service to do this?
I have used browsershots.org. Internet Explorer is very populair and there are long waiting lists for IE versions. Most of the time you will not see your screenshot before your 30 minutes will expire.
You can try www.litmussapp.com. They have software which checks css.
oeps typo: it should be www.litmusapp.com
I like Adobe Browserlab, even though it's annoying that you have to create an Adobe ID to use it.
Theres also Microsoft SuperPreview and our new service, Browsera. One issue we faced with browsershots is that it scrolls the window to collect the screenshot, resulting in abberations if you have fixed positioned elements, or background images that don't scroll.
I like to use the Total Validator Pro Desktop Tool and do everything in one big shot. Validation, WCAG, Screen shots, etc. The online version lets you do one screenshot at a time.
As most options in this question are no longer around I would like to suggest the cross browser testing solution BrowseEmAll which can be used for testing (especially IE) desktop and mobile browsers.
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