IE8下的60个bug

来源：60 bugs in IE8 for Windows

1- MSIE 8 requests automatically favicon.ico. Internet Explorer 8 should stop automatically requesting for favicon.ico in the root directory - a file which may not exist - and instead look for (fetch, HTTP request) an icon only and only if it's explicitly linked to from the webpage. The first time a user visits your Web page, Internet Explorer automatically searches for this [favicon.ico] file. Otherwise, when the favicon.ico does not exist, the error.log shows favicon.ico (hundreds of times) as "404 file not found". From a web standards and HTTP perspective, it does not make sense to request a file that has not been explicitly linked to begin with. This bug has been reported by several web authors since 1997!:

  • Dan's Web Tips: Titles, META Tags, LINK tags, and Search Engine Robots by Dan Tobias states: "MSIE automatically looks for 'favicon.ico' in the root directory of your site (which some webmasters find annoying if they have no desire to use an icon and don't like getting lots of '404 Not Found' errors in their log), some other browsers, like Mozilla, are more considerate and only look for an icon if it's explicitly linked."
  • Top 10 Bugs, Internet Explorer by Toby Inkster states: "Stop automatically requesting /favicon.ico and instead only request it when it's explicitly linked to from the page."
  • Web standards checklist, 6.4 Does the site have a favicon? by Russ Weakley states: "if they [favicon.ico] are not present, they can cause 404 errors in your logs (site statistics). Browsers like IE will request them from the server when a site is bookmarked. If a favicon isn't available, a 404 error may be generated."
  • The Dastardly "favicon.ico not found" Error by Linda Cole (August 1999) states: "No, you're not going crazy and no one is hacking into your site, adding mysterious little snippets for your error logs to report as missing. The dastardly "favicon.ico not found" that you see in your error logs is actually Internet Explorer 5 at work. IE automatically looks for a file it thinks you should have whenever someone creates a bookmark or a shortcut to a page on your site.(...) When the file is not found IE5 uses the default icon and you get an error message in your log files."

Firefox 1.x, Firefox 2.x, Firefox 3, Opera 9.x, Safari 2, Safari 3.0.2, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Konqueror 3.5.8, Galeon 2, Epiphany 2 all pass this test.

2- Favicon standardisation at Wikipedia, HTML 4 specification, rel attribute value (link-types) and the W3C Quality Assurance tip, How to Add a Favicon to your Site indicate that rel attribute must contain a space-delimited list of link types. Internet Explorer requires the rel attribute value "shortcut icon" when just "icon" is good enough for other browsers. So then, what does "shortcut" rel attribute value actually refers to then? rel="shortcut icon" will not be understood correctly (will be ignored in fact) by conforming web browsers. This issue was also mentioned and explained by Dan Tobias in his Dan's Web Tips: Titles, META Tags, LINK tags, and Search Engine Robots as follows: "MSIE looks only for 'shortcut icon'. Technically, a link attribute with multiple words is saying that the link is of multiple types, with each word being a different type identifier, but I think the Microsoft programmers were just clueless enough to think that spaces could be used within type names, and that 'shortcut icon' is what they think the type is."
'Shortcut icon' instead of 'icon', now that was definitely a simple oversight., from Eric Lawrence, IE program manager, at Jeff Davis' blog, why doesn't the favicon for my site appear in IE7?

Firefox 2.0.0.8, Firefox 3, Opera 9.50, Safari 3.0.3, Seamonkey 1.x, Seamonkey 2.0a1pre, Konqueror 3.5.8, K-meleon 1.x, NS 7.0, NS 7.2 all pass this test.

This bug has been reported at connect's IE beta feedback as bug 370225 by "ShadowChaser".

3- document.getElementById(SelectList[SelectIterator]).add(objOption, null);
add(objOption, null) does not work under Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8. Firefox 1.5, Firefox 2, Firefox 3, Opera 9.27, Opera 9.50, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x Seamonkey 2.x, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 388710.

4- DOM nodeType constant values are not listable, are not accessible Firefox 2.0.0.9, Opera 9.50, Safari 3.0.4, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 339307.

5- Support for cssFloat Firefox 2.0.0.9, Opera 9.50, Safari 3.0.4, Konqueror 3.5.8, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test.

6- Many DOM attributes are wrong This bug has been reported at connect's IE beta feedback as bug 348537.

7- Formatted alternate text is not implemented Alternate text for nonexistent images should be rendered as specified by markup code. If alternate text is to be rendered as inline, then it should inherit from its parent the inheritable properties, including font-size. This bug will still occur even if the Internet Explorer 7 or Internet Explorer 8 user has the Tools/Internet Options.../Advanced tab/Accessibility section/Always expand ALT text for images checkbox checked. Firefox 2.0.0.4, Opera 9.21, Konqueror 3.5.8, Amaya 9.55, Seamonkey 1.x, Seamonkey 2.x, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.

8- The value of usemap must match the value of the name attribute of the associated map element. This comes directly from the HTML 3.2 and HTML 4.01 spec. Firefox 2.0.0.5, Safari 3.0.2, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.

9- Rendering ALT text for images as inline and expanding the image placeholder dimensions as required by the alt text. When an image can not be displayed - for whatever the reasons -, then the alt text should be rendered as inline and image frame/placeholder dimensions should be ignored. Firefox 2.0.0.6, Amaya 9.55, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.2, NS 7.0, NS 7.2 all pass this test.

10- Images should be underlined in the following testcases:

Firefox 2.0.0.6, Safari 2.0.4, Safari 3.0.3, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.0a1pre, K-meleon 1.x, Galeon 2, Epiphany 2, NS 7.2 all pass these 3 tests.

This bug 10 has been closed because it turns out it is INVALID for CSS 2.1 while CSS 3 text module (latest Working Draft: 6 March 2007 does not yet identify such expected result.

11- Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 do not correctly support Number.toFixed() for numbers in the ranges {(-0.94,-0.5], [0.5,0.94)}: Number.toFixed() demo Firefox 2.0.0.8, Opera 9.50, Safari 3.0.3, Konqueror 3.5.x, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.1, NS 6.2, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16 all pass this test.

12- Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 do not support favicon of type image/png (or of other types of image like gif): favicon of type image/png demo. A favicon (or web site icon) image in png (a PNG is an official W3C web standard) or in gif image format are not supported by Internet Explorer for specifying favicon; only the .ico file format for specifying a favicon is supported by Internet Explorer. This is clearly insufficient.
Jeff Davis, IE project manager in his why doesn't the favicon for my site appear in IE7? states "It must actually be a .ico (an Icon) file. Bitmaps, pngs, gifs, etc, will not work.".
How to Add a Shortcut Icon to a Web Page at MSDN states "To create the icon, use an icon editor, such as the one included in Microsoft Visual Studio, and save the icon in the .ico file format. Internet Explorer will ignore icons that are not in .ico format, and will instead display the default Internet Explorer shortcut icon.".
Firefox 2.0.0.8, Firefox 3, Opera 9.50, Safari 3.0.3, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.0a1pre, K-meleon 1.x, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16 all pass this test. This bug has been reported at connect's IE beta feedback as bug 370228 by "ShadowChaser".

13- Image nested inside a label element with a for attribute unexpectedly does not transfert focus to its associated, targeted form control in Internet Explorer 7 and Internet Explorer 8. This bug applies to several form input controls and has been testcase-ed for the following elements: <input type="text">, <textarea> and <input type="checkbox">. Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.0.4, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. Credit must go to Batiste Bieler for discovering, reporting this bug and for providing a testcase on this precise bug. This bug has been reported at connect's IE beta feedback as bug 348575.

14- DOM 3 Core textContent support. Firefox 1.5, Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Konqueror 4.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 334438. This bug has been closed by the IE team and has not been reopened.

15- Closing non-script-initiated single-tab windows and tab instances According to MSDN, non-script-initiated single-tab windows and tab instances should not be closed by javascript without first getting an explicit consent from the user via a prompt confirmation window (dialog box). Firefox 2.x, Firefox 3.x, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.22, Galeon 2.0.4 all pass this test by refusing to close the window and by notifying so in the error console. This bug has been reported at connect's IE beta feedback as bug 379310.

16- event.offsetX, event.offsetY are mouse coordinates relative to padding-box of target node, not relative to content-box of target node. Internet Explorer 6 and Internet Explorer 7 were calculating event.offsetX and event.offsetY coordinates relative to the padding-box of target node. These coordinate references are also what the W3C CSSOM View Module Reference specify for event.offsetX and event.offsetY. Internet Explorer 6, Internet Explorer 7, Safari 3.1, Konqueror 3.5.8 all pass this test. This is a regression. This bug has been reported at connect's IE beta feedback as bug 362142.

17- getAttribute("style") on an element returns extended form of parsed CSS rules in IE8, not the string of content attribute or string of current textual value As noted by Peter-Paul Koch in his DOM compatibility table for attributes on getAttribute() and as noted by many web authors, when querying getAttribute("style") on a node, Internet Explorer 6, Internet Explorer 7 return an object and not a string. In IE 8 final release, though, things have improved. IE 8 final release will return a string which is the extended form of the textual parsable CSS rule from the author. Browsers currently do not stringnify internally CSS rules the same way: this is particularly true in cases when shorthand form is used. DOM 2 CSS, section 2.3 Interface CSS2Properties states "When dealing with CSS 'shorthand' properties, the shorthand properties should be decomposed into their component longhand properties as appropriate, and when querying for their value, the form returned should be the shortest form exactly equivalent to the declarations made in the ruleset." Firefox 1.5, Firefox 2.x, Firefox 3, Opera 9.50, Safari 3.1, Konqueror 3.5.8, NS 7.0, NS 7.2, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 427773.

18- rules="all" attribute specification not supported in border-collapse: separate tables There is nothing in the HTML 4.01 reference that prevents or hampers a border-collapse: separate table from rendering table rules around table cells when rules="all" is specified. Internet Explorer 6, Internet Explorer 7, Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 2.0.4, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This is a regression. This bug has been reported at connect's IE beta feedback as bug 409470. This bug has been closed by the IE team and has not been reopened.

19- An unclosed <p> immediately preceding a form element should be implicitly closed by IE when parsing and building DOM tree. This bug report is very much similar to the implicit closing on an unclosed <p> element when it encounters a <table>. Firefox 2.0.0.13, Opera 9.27, Opera 9.50, Safari 3.1, Konqueror 3.5.8, Amaya 11 build 20081216, Seamonkey 1.x, Seamonkey 2.x, NS 7.2 all pass this test. Credit must go to Jukka Korpela for discovering, figuring out and reporting this bug thanks to his Unclosed <P> before a form webpage testcase. This bug has been reported at connect's IE beta feedback as bug 338580.

20- @import-ing a style sheet for "print" fails in IE 7 and in IE 8. Firefox 2, Firefox 3, Opera 9.27, Opera 9.50, Safari 3.1.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, NS 7.0, NS 7.2 all pass this test. This bug has been reported at connect's IE beta feedback as bug 354316.

21- Inherited margin with inherit keyword: the parent's computed value should be inherited. Internet Explorer 8 does not use the margin-left computed value of the parent. Firefox 2.0.0.14, Firefox 3, Opera 9.27, Opera 9.50, Safari 3.1.1, Konqueror 3.5.9, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 344787.

22- An HTML comment before doctype declaration and after xml declaration triggers backward-compatible rendering mode in IE 7 and IE 8. This bug has also been reported in A comment before the doctype triggers quirksmode in IE7 by Alan Gresley. Firefox 1.5, Firefox 2, Firefox 3, Opera 9.x, Safari 3.1.2, Safari 4.0, Konqueror 3.5.9, Hv3 TKHTML alpha 16, Amaya 10.0.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.x, Epiphany 2.x all pass this test. Credit must go to Ingo Turski for discovering and reporting this bug at IE blog on March 6th 2008 and to Dean Edwards for discovering and reporting this bug at IE blog on September 15th 2005. This bug has been reported at connect's IE beta feedback as bug 354956.

23- objOption.defaultSelected = true is not supported by Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8. Mozilla 1.x, Firefox 1.x, Firefox 2.x, Firefox 3, Netscape 7.x, Seamonkey 1.x, Seamonkey 2.x, Safari 2.x, Safari 3.1, Safari 4.0, Konqueror 3.5.9, Opera 8.x, Opera 9.27, Opera 9.50, K-meleon 1.x, Galeon 2.x, Epiphany 2.x all pass this test. This bug has been reported at connect's IE beta feedback as bug 365833.

5 more complex Ian "Hixie" Hickson CSS 2.1 testpages (which all failed in MSIE 8)
link to actual test page IE 7 IE 8 Firefox 3.0 Opera 9.50 Safari 3.1.2 Konq 4.1.3 Other browsers which
pass the test page
link to actual test page IE 7 IE 8 Firefox 3.0 Opera 9.50 Safari 3.1.2 Konq 4.1.3 Other browsers which
pass the test page
24 border-width: inherit Fails Fails Passes Passes Passes Passes
25 Tall table with wide L-shaped floats Fails Fails Passes Passes Passes Passes NS 7.2
26 Stacking order: Floats and Blocks in Inlines Fails Fails Passes Passes Passes Passes NS 7.2
27 Cascade: Ordering test with various import techniques Fails Fails Passes Passes Fails Fails NS 7.2
28 CSS inheritance: border-color Fails Fails Passes Passes Fails Passes NS 7.2, Hv3 TKHTML alpha 16, Safari 4.0

29- Creating and inserting a command button before defining its type fails in Internet Explorer 7 and Internet Explorer 8. Firefox 1.5, Firefox 2, Firefox 3, Opera 9.27, Opera 9.51, Safari 3.1.2, Safari 4.0, Konqueror 4.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test.

30- font shorthand and inherit are incorrectly parsed and rendered in Internet Explorer 7 and Internet Explorer 8. "Shorthand properties take a list of subproperty values or the value 'inherit'. One cannot mix 'inherit' with other subproperty values as it would not be possible to specify the subproperty to which 'inherit' applied." coming from CSS 2.1, Appendix C. Changes, C.3.1 Shorthand properties. Firefox 2, Firefox 3, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 361182.

31- Incorrect parsing and rendering of font-size when involving system font in Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8. It seems that subsequent CSS declaration can not override one font subproperty of font shorthand when styled with a font system reserved name such as message-box. Nevertheless, CSS 2.1, section 15.8 Shorthand font property: the 'font' property states "System fonts may only be set as a whole; that is, the font family, size, weight, style, etc. are all set at the same time. These [font subproperty] values may then be altered individually if desired." Firefox 2, Firefox 3.0.1, Shiretoko 3.1, Opera 9.52, Safari 3.1.2, Konqueror 3.5.9, Amaya 11 build 20081216, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22.3 all pass this test. This bug has been reported at connect's IE beta feedback as bug 361181.

32- Unquoted font-family names must not contain unescaped parentheses ( ), unescaped square brackets [ ], unescaped curly braces { }, unescaped exclamation marks !, etc. Firefox 2, Firefox 3.0.1, Shiretoko 3.1, Safari 3.1.2, Konqueror 4.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22.3 all pass this test. Opera 9.52 fails 4 tests out of 16. This bug has been reported at connect's IE beta feedback as bug 361953.

33- <object> does not support natively PNG image if content-type (MIME type) is not specified; another testcase for bug 389191 Object-as-Image: (...) If no type is given, then Internet Explorer must try to determine what the object is based on any additional attributes provided (classid, codetype, etc.) or solely by the URL if no additional attributes are provided (by getting MIME type information from the server). (quote from HTML Improvements and Acid2: Internet Explorer 8 Beta 1 for Developers, page 4, available from Internet Explorer 8 Beta 1 Whitepapers). This testcase comes from Antti "sairwas" N?yh?'s Object, Images test suite (1999). Firefox 2.x, Firefox 3.0.3, Opera 9.60, Safari 3.1.2, Konqueror 4.1.1, Amaya 11 build 20081216, Seamonkey 2.x, NS 7.2, K-meleon 1.x all pass this test. This bug has been reported at connect's IE beta feedback as bug 389191.

34- Dynamically moving a DHTML layer with unitless offset position values should fail IE 8 must not honor unitless offset position values when in web standards compliant rendering mode (when document.compatMode == CSS1Compat). All modern browsers (even IE 6) do not honor unitless offset position values when specified declaratively. So I am submitting that unitless offset position values should not be honored when specified dynamically via script: such values should be ignored. Firefox 3.0.3, Safari 3.1.2, Safari 4.0, Konqueror 4.1.2, K-meleon 1.x, NS 7.2, Seamonkey 2.x all pass this test. This bug has been reported at connect's IE beta feedback as bug 381347.

35- An HTML comment before the doctype declaration will trigger IE 7 and IE 8 into backward-compatible "quirks" rendering mode when it should not do so. Firefox 1.5, Firefox 2.x, Firefox 3.0.4, Opera 9.62, Safari 3.2, Safari 4.0, Konqueror 3.5.10, Konqueror 4.1.1, Hv3 TKHTML alpha 16, Amaya 10.0.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.7, Epiphany 2.22 all pass this test. This bug has been reported at connect's IE beta feedback as bug 382800.

36- Inaccurate CSS parsing of cursor: url() declarations Firefox 1.5, Firefox 2.x, Firefox 3.x, Safari 3.0.4, Safari 3.2, Konqueror 3.5.8 all pass this test. This bug has been reported at connect's IE beta feedback as bug 407963.

37- Dynamic magnification of an image makes content grow outside padding-box and outside border-box Additionally, the border-width unexpectedly increases or decreases while it should remain 2px. This is a regression. Internet Explorer 7, Firefox 1.5, Firefox 2.x, Firefox 3.x, Opera 9.x, Safari 3.0.4, Safari 3.2, Konqueror 3.5.8, NS 7.2, Seamonkey 2.x all pass this test.

38- SelectElement.value should return the value which would be submitted, if the user had clicked the submit button Another testcase for this bug is initial value of the 'value' attribute of <option> is not set to the contents of the element by Nisse Engstr?m. Credit must go to Kyle Mulin for explaining this bug and for providing an initial, working testcase along with useful explanations, details in IE Blog in January 20th 2006. Firefox 1.x, Firefox 2.x, Firefox 3.0.5, Opera 9.63, Safari 2, Safari 3.2, Konqueror 4.1.2, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test. This bug has been reported at connect's IE beta feedback as bug 389742.

39- Submit button value not posted with form submission A form with 1 input for text and 1 input for a submit button will only post the input text value and not the submit value when the user hits the Enter key from the input text. Credit must go to Mikey for defining and explaining this bug in IE Blog on December 18th 2008. Firefox 1.x, Firefox 2.x, Firefox 3.0.5, Opera 9.63, Safari 2, Safari 3.2, Konqueror 4.1.2, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test. This bug has been reported at connect's IE beta feedback as bug 389736. This bug had been previously filed and reported as bug 362726 but was unfortunately closed (not reproducible) and was not reactivated.

40- Ignore font sizes can affect accessibility to content None of this happens in all other non-IE browsers: resizing font size or ignoring font sizes specified on webpages does not affect, should not affect or should not interfere with accessibility to content. This bug has been reported at connect's IE beta feedback as bug 399794.

41- Horizontal formatting of horizontal line Text-align should not affect horizontal formatting of <hr> while margin-left should in Internet Explorer 8. Firefox 2.0.0.8, Firefox 3.0.5, Safari 3.0.3, Konqueror 3.5.2, Konqueror 4.1.3, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.20, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16, Amaya 9.55 all pass both of these tests. This bug has been reported at connect's IE beta feedback as bug 408027.

42- Bullet (filled disc) list-markers are misrendered when using MS Sans Serif font A normal bullet (filled disc) should be rendered for list items. Instead, IE 8 RC1 build 18372 renders a bullet list-marker as a thin vertical bar. This is a regression. This bug seems to arise from a mismapping of the bullet character entity in some MS fonts. Internet Explorer 7, Firefox 3.0.6, Opera 9.63, Safari 3.2, Konqueror 4.1.3, Seamonkey 2.x all pass this test. Credit must go to Philip A. Hagen for originally discovering and reporting this bug. This bug has been reported at connect's IE beta feedback as bug 413039. This bug has been closed by the IE team and has not been reopened.

43- clientLeft DHTML object property value is incorrect in rtl overflowed content box Steps: load the URL, then click on the "right to left" radio button. Actual results in IE 8 RTW build 18702: clientLeft value remains at 24. Expected results: clientLeft value should change from 24 to 41. This is a regression. Internet Explorer 7, Firefox 3.0.6, Seamonkey 2.x all pass this test. This bug has been reported at connect's IE beta feedback as bug 413852.

44- CPU hangs (infinite loop) when examining read-only properties in Developer tools Initial condition: First, have the Windows Task Manager opened (right-click on the task bar and then select Task Manager). Steps to reproduce: 1- Load Mark "Tarquin" Wilton-Jones' page IE 8 and Object Tags 2- Do Tools/Developer Tools (F12) 3- In the HTML tab, click the [+] in front of <html>, <body>, <div class="bodyarea">, then click the [+] in front of <p class="demo"> and then click the <object> to select it, to highlight it. You should have navigated to <object data="tick.html" width="80%" height="55" type="text/html" altHtml="Your browser could not display the image, so it is displaying this text instead"/> 4- In the right pane, click the Attributes button 5- At the bottom, check the "Show Read-Only Attributes" checkbox. Actual results in IE 8 RC1 build 18372: %tage of CPU activity for iexplore.exe process is maximized and remains maximized. This is a serious issue. This bug has been reported at connect's IE beta feedback as bug 414807.

45- border-style: inset | outset | ridge | groove not rendered as expected for black color Currently, test 6405, test 6406, test 6407 and test 6408 fail. This bug had been already reported 11 years ago by richinstyle.com: 3D styles rendered as solid when border-color is dark and 3D border styles rendered as solid when color is dark. This bug has been reported at connect's IE beta feedback as bug 414815. This bug has been closed by the IE team and has not been reopened.

46- Dynamically setting clip: auto does not reset a clipped container overflowed by its block child content appropriately Credit must go to Vadikom-Vasil Dinkov "vasko_dinkov" for originally discovering and reporting this bug. This bug has been reported at connect's IE beta feedback as bug 415011.

47- Embedded HTML document in an <object> unexpectedly creates a vertical scrollbar by Mark "Tarquin" Wilton-Jones: "for reasons best known to itself, [IE 8 RC1 build 18372] choses to display scrollbars in the demo on this page." This bug has been reported at connect's IE beta feedback as bug 415028.

48- Embedded HTML document in an <iframe> unexpectedly creates a dimmed, inactive vertical scrollbar. 1 example where this occurs: test 6772 This bug has been reported at connect's IE beta feedback as bug 415037.

49- Defining font-size with ex length unit must refer to computed font-size of the parent element Firefox 2.x, Firefox 3.0.11, Opera 9.64, Safari 4.0, Konqueror 3.5.8, Konqueror 4.2.4, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test.

50- visibility: inherit applied to command button fails in IE 8 This bug was originally discovered by Fredrik "DXter" Jonsson and reported at launchpad's bug 345777. This is a regression. Internet Explorer 7, Firefox 2.x, Firefox 3.0.11, Opera 9.64, Safari 4.0, Konqueror 3.5.8, Konqueror 4.2.4, Seamonkey 1.x, Seamonkey 2.x, NS 7.2, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test.

51- Text-align should only format inline content of a list-item's principal block box Text-align: center or text-align: right should only affect inline content of a list item's principal block box and not the position of its list marker when the list-item's list-style-position is set to outside. Safari 4.0 and Konqueror 4.2.4 pass this test.

52- A floated image in a list-item overlaps or masks or removes its list-marker Firefox 3.5 and NS 7.2 pass all 3 tests; Opera 9.64, Safari 4 and Konqueror 4.2.4 pass only the 3rd test.

53- Overlapped background-image with transparent animated gif does not get repainted accordingly This bug was originally reported by ahacks.com web developer and explained in IE Blog on July 3rd 2009. Firefox 3.5, Opera 9.64, Safari 4, Konqueror 4.2.4 and NS 7.2 pass this test.

54- Block-level, replaced elements with width: auto;, margin-left: auto; and margin-right: auto; should be centered within their respective parent block-level elements This bug was originally reported by stusmith at Stackoverflow.com Blog on March 19th and 29th 2009. This is a regression. Internet Explorer 6, Internet Explorer 7, Firefox 3.5.2, Opera 9.64, Safari 4.0.3 and Konqueror 4.2.4 pass both of these 2 tests.

55- CRASH in IE 8 with findText() in a text range This bug was originally reported by Anoakie at htmlbugs.com blog on April 9th 2007 as affecting IE 6 and IE 7. Now, we can see this bug happens as well in IE 8. What is surprising and upsetting is that a perfectly valid HTML 4.01 markup code with a declared strict DTD webpage of 440 bytes can crash like that. It's quite possible that the original bug report from Anoakie at htmlbugs.com was not investigated by IE Team in the process of developing IE 8.

56- Incorrect default attribute selector parsing. Firefox 3.5.2, Opera 10.0, Safari 4.0.3, Konqueror 4.3.1, NS 7.2 and Seamonkey 2.x pass this test.

57- Descendants of a "visibility: hidden" ancestor element must be visible if they have "visibility: visible". This is a regression. Internet Explorer 7, Firefox 3.5.3, Opera 10.0, Safari 4.0.3, Konqueror 4.3.1, NS 7.2 and Seamonkey 2.x pass this test.

58- Intra-table navigation thanks to fragment identifier fails. Navigating from a link into a table to a linked table-row with an id attribute should succeed. This is a regression. Credit must go to BootNic for initially, originally reporting this bug in alt.html thread "IE 8 Table Row Anchor" and to Andreas Prilop in comp.infosystems.www.authoring.html thread "ID attribute for table row". Internet Explorer 7, Firefox 3.5.5, Opera 10.01, Safari 4.0.4, Konqueror 4.3.3, NS 7.2 and Seamonkey 2.x pass this test.

59- Margin-top of block-level element is incorrectly substracted when calculating clearance. Margin-top of block-level element is incorrectly substracted when calculating clearance for a preceding empty content block on which "clear" is set. Other variations of this bug are: Margin-top of block-level element is incorrectly substracted when calculating clearance with a right-floated preceding sibling block and Margin-top of block-level element is incorrectly substracted when calculating clearance with 2 left-and-right-floated preceding sibling blocks. Credit must go to InventPartners for originally discovering and reporting this bug in Internet Explorer 8: Top margin missing from first element after floated elements and clearing <div> Firefox 3.6, Opera 10.10, Safari 4.0.4 and Seamonkey 2.x pass this test.

60- Quoted -ms-filter Alpha opacity value interferes with float rendering layout. When quoting -ms-filter value, floats are misrendered. This bug happens on other -ms-filter values, not just with -ms-filter: progid:DXImageTransform.Microsoft.Alpha(opacity=). This bug was originally reported at eggheadcafe's post Bug: IE8 Standards Mode Float Mode on december 29th 2009. Firefox 3.6, Opera 10.10, Safari 4.0.4, Konqueror 4.3.4 and Seamonkey 2.x pass this test.

加支付宝好友偷能量挖...


评论(0)网络
阅读(132)喜欢(0)HTML/CSS兼容/XML