Tuesday, July 15, 2008

IE8 is out

Internet explorer 8 is out in its beta phase.

Some of its features are--

1. Users can set three different rendering modes using the X-UA-Compatible header:
  • Quirks mode which supports Internet Explorer 5 and legacy browsers
  • Strict mode which supports Internet Explorer 7 and is accessed through the emulate IE 7 button
  • Internet Explorer 8 standards mode
The default will be standard mode.

2.

Cascading style sheets 2.1 compliance

The Internet Explorer 8 layout engine is built to be cascading style sheets 2.1 compliant, enabling web developers and designers to write their pages once and have them render properly across all cascading style sheets 2.1 compatible browsers.

HTML improvements

Many cross-browser inconsistencies have been fixed in Internet Explorer 8 Beta 1, including:

  • Separate URL handing for attributes.
  • The get/set/remove attribute implementations are now compatible with those of other browsers.
  • Default attributes for HTML are supported so that they always exist on elements whether specified in the markup or not.

Improved namespace support

Internet Explorer 8 simplifies the use of standards-compliant XML-based webpages that support namespace features like scalable vector graphics, XML user interface language, mathematical markup language, and others.

Platform performance improvements

Internet Explorer 8 Beta 1 improves performance in many Internet Explorer subsystems, such as the HTML parser, cascading style sheets rule processing, markup tree manipulation, the JScript parser, garbage collector runtime, and memory management.

Developer tools

The new Developer Toolbar enables developers to quickly debug HTML, cascading style sheets, and JavaScript in a visual development environment that is included with the web browser. Developers can quickly identify and resolve issues because of the deep insight the tool provides into the Document Object Model. The Developer Toolbar also allows the layout to be changed on the fly so that each rendering scenario can be tested thoroughl

No comments: