Wednesday, November 14, 2012

Answers > What Is Browser Incompatibility? How It Can Be Handled Using XHTML and CSS?

What Is Browser Incompatibility? How It Can Be Handled Using XHTML and CSS?

by nForms on December 3, 2011

What is Browser Incompatibility? How it can be handled using XHTML and CSS?

Tags: , , , , , ,

Similar XForms | XML Posts

{ 2 comments… read them below or add one }

Fasty July 18, 2011 at 9:35 pm

Browser incompatibility is a term used mostly when you have a portable device with internet capabilities, such as cell phones and Black Berries, that are having trouble accessing a web page; usually because it was created with regular HTML, not XHTML.

The only real difference between XHTML and HTML is XHTML’s designed for small portable devices and small stripped down browsers. Most web designers use XHTML nowadays because it is considered the more advanced way. HTML still works fine though.

Everything written above can easily be learned from Google.

A good site is: http://laurasbasicstowebdesign.com/webdesignblog/

David Karr July 18, 2011 at 9:35 pm

I would guess you’re referring to the notion that web pages that are built without considering portability issues between browsers could work fine on one browser or platform, but display various problems when run on other browsers or platforms. This is because each browser company made their own decisions about what pieces of the various standards they would implement, and how they would implement them. In addition, each browser company implemented custom tags, functions, and components which are not available at all on other browsers.

The CSS implementation in IE has some capabilities for cross-browser compatibility, as IE defines certain formatted comment structures that are recognized as valid CSS directives in IE, but other browsers consider them comments.

I’m not aware of any facilities in XHTML that specifically allow for cross-browser compatibility.

Javascript has two basic features that allow for it, being "browser detection" and "feature detection". The latter simply means that you see whether certain objects are defined in Javascript, and that tells you whether the running Javascript implementation supports certain features. The former tries to determine what browser is running, which spawns a large number of other decisions. In general, if you’re hand-coding checks, feature detection is better. If you’re using the Google Web Toolkit (GWT), that does browser detection internally, which allows it to simply serve different Javascript files, which is more efficient than if it had to do feature detection each time it needed to use a particular feature.

Previous post:

Next post: