- D2D Rendering
In rare circumstances, the IE Platform Preview may render Web page content incorrectly or slowly on some older graphics cards. You may see page content garbled or page scrolling may be slow. Though this issue is known and being fixed, we would still like to hear about your specific issues.
Please use the ‘Report an Issue’ feature in the Platform Preview to bring this issue to our attention. Be sure to include the output file created by running IE Diagnostics in the Platform Preview’s Report Issue menu.
To work around the issue while running the Platform Preview, please download and run the "Force D2D Software Mode" registry file and restart the Platform Preview. To switch back to graphics card based rendering again, please download and run the "Force D2D Hardware Mode" registry file and restart the Platform Preview.
- getComputedStyle box model properties
getComputedStyle is available in the platform preview builds but does not currently support any box model properties.
- addEventListener event registration
Many events corresponding to the existing Event interface are not currently hooked up, including DOMContentLoaded. When an event type registered through addEventListener is not hooked up, a notification will be posted to the Developer Tools Console window indicating that the event is not supported.
- SVG Performance
In general, performance with “normal” SVG files is good. However, performance work on large or complex SVG files is not yet complete. You will see this most with CAD- or GIS-generated SVG images.
- XML Parsing Errors (affects XHTML and SVG)
No notifications are currently displayed for XML parsing errors encountered while parsing XHTML or SVG. Note that even without notifications, parsing correctly stops and only content occurring before the error is rendered on the page.
- Issue 541443: Empty attribute selection change is unversioned.
Description: There was a fix made in IE9 to conform to the CSS3 selectors spec in regards to how to handle empty attribute selectors (http://www.w3.org/TR/CSS2/selector.html#attribute-selectors).
Previously, given the selector [attr], IE would not match the following elements:
<element attr = ''>
<element attr>
Now in IE9 mode these elements will match the selector, however, this fix was not versioned correctly and is currently being applied in IE7 and IE8 modes as well. This means that the behavior with this selector will be different browsing IE8 and IE7 mode pages in IE9 than it would be if you browsed those pages in IE8 or IE7.
Workaround: If you really need this selector not to match your elements in IE7 or IE8 mode you can remove the attribute from the element.
- Issue 541445: rgba() bleeds into legacy modes
Description: The new rgba() color notation works in quirks, 7, and 8 document modes. In future versions of IE9, this syntax will only apply in the browser's most standard mode.
- Issue 541453: Platform Preview does not list any supported mime-types in the Accept header for outgoing requests
Description: The Windows Internet Explorer Platform Preview does not currently report supported MIME types when requesting resources from a web server. This can impact server-side detection scripts that pivot content based on the presence of specific MIME-types, such as "application/xhtml+xml".
- Issue 541446: Floating-point properties won't parse values without a leading zero
Description: CSS floating point values which are less than 1, do not parse correctly if they do not include the leading 0. For example "0.5" will parse correctly but ".5" will not.
Workaround: Include the leading zero for floating point values which are less than 1.
- Issue 541450: Properties still using currentStyle behavior for getComputedStyle
Description: There are a few properties where the values returned by getComputedStyle are not yet converted from relative units to absolute units. These properties include:
backgroundPosition (both X and Y)
borderSpacing
fontSize
letterSpacing
lineHeight
textIndent
verticalAlign
wordSpacing
- Issue 541444: Network inspector is missing compression information
Description: The network inspector is showing the uncompressed size of HTTP request and is not indicating if the requests were compressed (gzip/deflate). All requests seem to be sent uncompressed even though they were sent compressed.
- Issue 541449: Browser Mode shows ‘Unknown’ in Developer Tools
Description: When the Platform Preview is opened, a page is loaded, and the Developer Tools are started, the Developer Tools always show 'Unknown' for Browser Mode. You may still change the Browser Mode using the drop down and have the value applied. However, the new Browser Mode value will show in the Developer Tools even when you navigate to a new page that has a different browser mode.
- Issue 541447: Re-opening the Developer Tools after closing fails on the first try
Description: If you open and then close the Developer Tools, the next time you try to open the Developer Tools (either through the F12 key or through the Debug menu) the first attempt fails. You must click the menu item or hit the F12 key a second time for the Developer Tools to open.
- Issue 541448: Insert Breakpoint is not inserting Breakpoint at desired location
Description: In some cases when adding a breakpoint the breakpoint is inserted at a different statement than the one intended.
Workaround: If the problem persists developers can use the JavaScript reserved word "debugger" in their script to hit a breakpoint, for example:
var foo = 0;
debugger;
var bar = 2 / foo;
- Issue 541440: Developer Tools does not list 'border-radius,' 'border-
-radius' properties
Description: The Developer Tools Style and Trace Styles panes may show the border-radius property with a value of 0px 0px 0px 0px and a strikethrough even though the property is not applied to this element anywhere in the cascade.
- Issue 541791: Initial Web Request is not captured
Description: While captuing network traffic the first request for a page is missing. This only happens when navigation is caused by following hyper links.
Workaround:To capture all traffic you can clear the browser cache and then refresh the page or use address bar at ctrl+0.