Browsers
As the internet was created to unite the world into one inter connecting community, the use of so many different browsers that view Web pages in different ways makes it harder for a Web designer to create a Web site and it can stop users seeing a Web page in the same way. When designing a Web site, the designer must test their pages in different browsers to check the outcome of that page. With so many browsers available, it is important to consider which browsers to test for and how many past browser versions need to be catered for within the designs.
As technology has advanced, the situation has improved to that of a few years ago but the problem has not been completely resolved. You can now be confident that at least 99% of users have browsers that support nearly all of HTML 4. However, there are still inconsistencies in the way Cascading Style Sheets are implemented and older browser versions pre-dating the current standards take a long time to fade away entirely. A Web site designer must now also consider the mobile user; phones, PDAs and other handheld media devices that have access to the internet. The browser that these devices use will be a variant of a standard browser but the user will view the pages on a much smaller screen. A mobile browser, also called a micro browser, mini browser or wireless internet browser (WIB) are optimised so as to display Web content most effectively for small screens on portable devices. Mobile browser software must also be small and efficient to accommodate the low memory capacity and low-bandwidth of wireless handheld devices. Typically, they were stripped-down Web browsers but as of 2006 some mobile browsers can handle latest technologies such as CSS 2.1, JavaScript and Ajax. Jennifer Niederst Robbins (2006) says;
"1996 to 1999: The Browser Wars begin.
For years, the Web development world watched as Netscape and Microsoft battled it out for browser market dominance. The result was a collection of proprietary HTML tags and incompatible implementations of new technologies, such as JavaScript, Cascading Style Sheets, and Dynamic HTML. On the positive side, the competition between Netscape and Microsoft also led to the rapid advancement of the medium as a whole."
The World Wide Web consortium establishes the basic rules on how to translate a HTML document and the official HTML standards.
The HTML standards say that the Table tag should support a Cellspacing attribute to define the space between parts of the table. HTML standards don't define the default value for that attribute, so unless you explicitly define Cellspacing when building your page, two browsers may use different amounts of white space in your table. HTML standards are usually ahead of what browsers support. Over the past few years Internet Explorer has done a much better job of this than Netscape Navigator, though Opera has done arguably the best job.
If you build a Web page and the user's browser does not understand part of the language, then they will ignore that part and continue creating the rest of the page. This will cause some browsers not to display the page the way it was designed to be seen.
Source: http://goo.gl/chKBD
As the internet was created to unite the world into one inter connecting community, the use of so many different browsers that view Web pages in different ways makes it harder for a Web designer to create a Web site and it can stop users seeing a Web page in the same way. When designing a Web site, the designer must test their pages in different browsers to check the outcome of that page. With so many browsers available, it is important to consider which browsers to test for and how many past browser versions need to be catered for within the designs.
As technology has advanced, the situation has improved to that of a few years ago but the problem has not been completely resolved. You can now be confident that at least 99% of users have browsers that support nearly all of HTML 4. However, there are still inconsistencies in the way Cascading Style Sheets are implemented and older browser versions pre-dating the current standards take a long time to fade away entirely. A Web site designer must now also consider the mobile user; phones, PDAs and other handheld media devices that have access to the internet. The browser that these devices use will be a variant of a standard browser but the user will view the pages on a much smaller screen. A mobile browser, also called a micro browser, mini browser or wireless internet browser (WIB) are optimised so as to display Web content most effectively for small screens on portable devices. Mobile browser software must also be small and efficient to accommodate the low memory capacity and low-bandwidth of wireless handheld devices. Typically, they were stripped-down Web browsers but as of 2006 some mobile browsers can handle latest technologies such as CSS 2.1, JavaScript and Ajax. Jennifer Niederst Robbins (2006) says;
"1996 to 1999: The Browser Wars begin.
For years, the Web development world watched as Netscape and Microsoft battled it out for browser market dominance. The result was a collection of proprietary HTML tags and incompatible implementations of new technologies, such as JavaScript, Cascading Style Sheets, and Dynamic HTML. On the positive side, the competition between Netscape and Microsoft also led to the rapid advancement of the medium as a whole."
The World Wide Web consortium establishes the basic rules on how to translate a HTML document and the official HTML standards.
The HTML standards say that the Table tag should support a Cellspacing attribute to define the space between parts of the table. HTML standards don't define the default value for that attribute, so unless you explicitly define Cellspacing when building your page, two browsers may use different amounts of white space in your table. HTML standards are usually ahead of what browsers support. Over the past few years Internet Explorer has done a much better job of this than Netscape Navigator, though Opera has done arguably the best job.
If you build a Web page and the user's browser does not understand part of the language, then they will ignore that part and continue creating the rest of the page. This will cause some browsers not to display the page the way it was designed to be seen.
Source: http://goo.gl/chKBD
Post a Comment