|
|
8 for Windows1- 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!:
Firefox 1.x, Firefox 2.x, 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 and Architecture of the World Wide Web, 2.5 URI opacity state that the href of a favicon should point to any URL and not be limited, not be restrained to the location of /favicon.ico (at root of server). "The use of a reserved location on a website conflicts with the Architecture of the World Wide Web, and is known as link squatting or URI squatting." The document W3C Quality Assurance tip, How to Add a Favicon to your Site and siteData-36 state that identifiers on a web site should be entirely under the control of the owner/publisher of the domain name.
3- Last character non-text-selectable with mouse if ponctuation character Exclamation mark, period, comma, etc. are not text selectable (highlightable) with mouse-dragging. Internet Explorer 7, Firefox 2.x, Opera 9.x, Safari 2, Safari 3.0.2, Konqueror 3.5.8, NS 6.1, NS 6.2, NS 7.0, NS 7.1, NS 7.2, Hv3 TKHTML alpha 16 all pass this test.
4- Background shorthand with rgb() and background-image is buggy and Background shorthand with rgb() is buggy All credit must go to Nicole's IE8 Beta - Broken RGB Color. The problem has also been reported by Patrick Blackstone with his CSS Background Properties Shorthand with RGB Color Bug testcase and by Jeremy Smith's IE8 Background repeat-x CSS Bug.
5- Table header cells should be vertically aligned in the middle, not at the top. This is a regression.
6- A disabled button should not fire onclick events Similarly, disabled attribute is not supported, not implemented. This is a regression.
7- defaultChecked for radio button is not implemented. This is a regression.
8- alt attribute for image is displayed in a tooltip testcase by Simon Pieters. Internet Explorer implements incorrectly the alt attribute (versus the title attribute). This bug has been reported and documented for well over 10 years now:
This bug has been reported at connect's IE beta feedback as bug 334225.
9- <q> element is not supported. Q element testcase from (DRAFT) HTML4 Test Suite
"Visual user agents must ensure that the content of the Q element is rendered with delimiting quotation marks."
coming from HTML 4.01 spec., section 9.2.2 Quotations, Rendering quotations. This absence of support has also been explained and testcase-ed by Aaron Gustafson in his Support Q in IE.next Wishlist
10- Non-defined value of option is not set to the contents of the OPTION element Firefox 1.x, Firefox 2.x, 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. Another interesting 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.
11- Id versus name when using getElementById is incorrectly implemented. This bug has been reported by many people, including Peter-Paul Koch and this bug has now been reported on Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8.
12- When HTML 4 rules attribute is defined for rows, cols or groups, then the border-collapse value must be collapse in CSS 2.1 Firefox 2.x, Opera 9.x, Safari 3.0.4, NS 7.2, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2, Epiphany 2 all pass these 3 tests.
13- tbody {height: 150px; overflow: auto;} does not work
14- 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.
15- 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 all pass this test. This bug has been reported at connect's IE beta feedback as bug 339307.
16- Support for cssFloat Firefox 2.0.0.9, Opera 9.50, Safari 3.0.4, Konqueror 3.5.8, Hv3 TKHTML alpha 16 all pass this test.
17- Many DOM attributes are wrong
18- Support of comma as separator in CSS 2.1 property clip: rect(valOffsetTop, valOffsetRight, valOffsetBottom, valOffsetLeft) Firefox 1.5.0.7, Firefox 2.0, Opera 9.02, Konqueror 3.5.4, Safari 2.0, Safari 3.0.2, NS 6.2, NS 7.0, NS 7.1, NS 7.2 and MSIE 5.5 all pass this test.
"Internet Explorer takes their usual route and ignores the required comma separated values and only supports the optional comma-less method. So, even though using commas is the correct method, you'll need to drop the commas in order for the clip property to work in Internet Explorer (even in IE7)." taken from Misunderstood CSS Clip by Nicholas Gagne. This is also reported in the tutorial Creating Thumbnails Using the CSS Clip Property by seifi.org in the following manner:
"The W3C recommendation suggests using commas between the coordinates, however this is broken in Internet Explorer. Strangely using the commas in IE does not work when in standards-compliant mode, but it does work when in quirks mode.".
19- Margin-top of cleared block (...)
20- Dynamically DOM-created and DOM-inserted form controls are not DOM-fetchable, not DOM-queryable This bug was also reported by Aaron Gustafson in Death to bad DOM Implementations in september 2005. "I just encountered a DOM implementation issue in IE which took about three hours to solve (and like a year off my life)." This bug is also mentioned, explained at Semicolon's "Setting the 'name' attribute in Internet Explorer" by Bennett McElwee.
21- Vertical-align: middle is incorrectly rendered. NS 6.1, NS 6.2, NS 7.0, NS 7.1, NS 7.2, Firefox 2.0.0.3, Seamonkey 1.x, Seamonkey 2.x, Epiphany 2.14, Safari 2.0.4, Safari 3.0.4 and Konqueror 3.5.5 all pass this test. Opera 9.26 and Opera 9.50 almost pass this test.
22- Links with display: block do not react to hover over their non-text part if previous block-level element has a negative margin-top. NS 6.1, NS 6.2, NS 7.0, NS 7.1, NS 7.2, Seamonkey 1.x, K-meleon 1.x, Firefox 1.x, Firefox 2.x, Safari 2.0, Safari 3.0.2, Opera 9.x, Konqueror 3.5.8, Hv3 TKHTML alpha 16, Galeon 2, Epiphany 2 all pass this test.
A similar problem/issue was explained in Sliding doors of CSS, part II in "A list apart" article, in October 2003
23- CSS columnar layout that fails in Internet Explorer 7 and Internet Explorer 8: 1st demo: resizing text size breaks this CSS columnar layout in MSIE 7. Firefox 2.0.0.4, Safari 3.0.2, Opera 9.21, Konqueror 3.5.8, NS 7.0, NS 7.2, Amaya 9.55, Hv3 TKHTML alpha 16, K-meleon 1.x, Seamonkey 1.x, Seamonkey 2.x, Galeon 2, Epiphany 2 all pass this test.
24- Miswritten system font reserved names are honored: Internet Explorer 7 and Internet Explorer 8 do not parse correctly miswritten system font reserved names. Firefox 2.0.0.4, Safari 2, Safari 3.0.2, Opera 9.21, NS 6.2, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16, K-meleon 1.x, Seamonkey 1.x, Seamonkey 2.x, Galeon 2, Epiphany 2 all pass this test.
25- hasAttributes() method is not supported. Internet Explorer 7 and Internet Explorer 8 do not support DOM 2 Core hasAttributes() method. Firefox 2.0.0.4, Safari 2, Safari 3.0.2, Opera 9.21, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.
26- DOM 1 Core and DOM 2 Core attributes NamedNodeMap implementation Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 do not implement correctly the attributes attribute as a list of specified attributes. Firefox 2.0.0.4, Safari 2, Safari 3.0.2, Opera 9.21, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.
27- Javascript reserved keyword const is not supported Internet Explorer 7 and Internet Explorer 8 do not support the javascript reserved keyword const used to declare and to define constants. Firefox 2.0.0.4, Safari 2, Safari 3.0.2, Opera 9.21, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.
28- OffsetHeight for dynamically created with document.write() is wrong Firefox 2.0.0.4, Safari 2, Safari 3.0.2, Opera 9.21, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.
29- Formatted alternate text is not implemented Alternate text for nonexistent images should be rendered as specified by markup code. 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, NS 6.2, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2, Epiphany 2 all pass this test.
30- A relatively positioned child is not clipped, hidden by parent with overflow: hidden. This bug has also been reported and described by Alan Gresley's Overflow hidden with relatively positioned child bug report and in connect's bug 332028 CSS overflow test by JackChapple. Firefox 2.0.0.5, Opera 9.22, 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.
"other bugs that we fixed: (...) Nested block elements now respect all overflow declarations (hidden, scroll, etc)" taken from IE Blog, Details on our CSS changes for IE7, August 22nd 2006.
31- 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.
32- CSS columnar layout that fails in MSIE 8: 3rd demo: because of its left: auto miscalculation offset bug, the navigation menu links at the top are incorrectly offset. Firefox 2.0.0.6, Safari 3.0.3, Opera 9.22, Konqueror 3.5.8, NS 6.2, NS 7.0, NS 7.2, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.x, Epiphany 2.x all pass this test. Hv3 TKHTML alpha 16 positions navigation menu links at the top with the correct offset but it does not render the whole webpage as expected.
33- Links in <ul> styled with display: block do not trigger :hover when hovering the mouse cursor over their non-text part. Additionally, a duplicate (phantom) list-marker bullet appears unexpectedly on the previous list-item when hovering over a list-item. Firefox 2.0.0.6, Opera 9.23, Opera 9.50, Safari 3.0.3, 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.1.2, Galeon 2.x, Epiphany 2.x all pass this test. This sort of bug happens often in CSS columnar webpage templates (e.g.: Bridge CSS columnar template and is reported often in newsgroups (e.g.: http://www.itzehoer.de/ in alt.html newsgroup forum discussion on May 4th 2007 under the subject line Link-Problem with IE7) and is one reason why amateur web authors resort to display: table-cell, bizarre hacks, ugly and non-forward-compatible hacks or/and even table-based layout design.
An example of regression for this type of bug: this basic layout with 3 columns by Gabriele Romanato. The links in the leftmost column are reactive even in the non-text parts of the links in Internet Explorer 7 but not so in Internet Explorer 8. This is a regression.
34- Vertical-align should NOT and must NOT apply to <ul> with list-style-image. Firefox 2.0.0.6, Opera 9.23, Opera 9.50, Safari 3.0.3, Konqueror 3.5.8, Seamonkey 2.0a1pre, Konqueror 3.5.2, Seamonkey 1.x, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.2, NS 7.0, NS 7.2 all pass this test.
35- 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.0a1pre, Seamonkey 1.x, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.2, NS 7.0, NS 7.2 all pass this test.
36- 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.
37- Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 fail to correctly position an image with background-position when it is defined with em: MSIE 7 background position bug demo. Firefox 2.0.0.7, Opera 9.50, Safari 3.0.3, Konqueror 3.5.5, Seamonkey 1.x, Seamonkey 2.0a1pre, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.2, NS 7.0, NS 7.2 all pass this test. Credit goes to Tim Snadden for his Internet Explorer Background Position Bug demo.
38- Internet Explorer 5, Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 beta 1 do not increase or decrease correctly nested block-level elements when they use font-size: 1em: EM text resizing bug demo. This is a widely known and very frequently encountered and reported bug in Internet Explorer 5, Internet Explorer 6 and Internet Explorer 7 . Basically, the problem with setting the font-size in EM is that increasing or decreasing text size will grow or shrink fonts out of proportion (exponentially) for nested block-level elements. Firefox 2.0.0.8, Opera 9.50, Safari 3.0.3, Konqueror 3.5.5, Seamonkey 1.x, Seamonkey 2.0a1pre, K-meleon 1.x, Galeon 2, Epiphany 2, NS 6.1, NS 6.2, NS 7.0, NS 7.2, Hv3 TKHTML alpha 16, Amaya 9.55 all pass this test. This bug has been reported at connect's IE beta feedback as bug 339085. This IE 5+ bug has been reported many times, in many newsgroup discussion forums on web authoring, in various webpages, blogs from web developers. It's really worth mentioning a few of them and quoting some highly relevant testimonials describing accurately the effects of this bug:
"IE gets its text resizing horribly wrong when just using ems. (...) bump the text size up or down, and you'll notice that IE scales ems far more drastically than percentages, resulting in too big / too small text."
from Patrick H. Lauke, May 18th 2004, Weblog comments: How to size text using ems
"text sized in ems can be resized across all browsers. However IE6 and IE7 unacceptably exaggerate the smallness and largeness of the resized text"
from Richard Rutter, November 20th 2007, How to Size Text in CSS
"However, (gasp) IE has a problem with ems. Resizing text from medium (default) to large in IE5/6 would lead to a huge increase in font size rather than the gradual one expected"
from Jon Tan, September 27th 2007, The Incredible Em & Elastic Layouts with CSS
"If for instance you set the root element (either <body> or <html>) to font-size:1em, then just setting View > Text Size to 'smaller' can cause the text to become unreadably small."
from css-discuss.incutio.com, 2007, UsingEms, A word of caution concerning Internet Explorer
"When I tried font-size:1em, my IE6 browser 'text size' will toggle from very tiny to very huge.
....Not acceptable for accessibility!"
from Krystof, August 29th 2005, Weblog comments: How to size text using ems
Only 2 people explained and documented this bug in detail (with screenshots, examples, demos):
39- 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.0a1pre, 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.
40- 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 Firefox 2.0.0.8, 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.
41- The last (in order of appareance) rule with same media, same importance, same origin, same specificity must prevail demo. According to CSS 2.1, section 6.4.1 Cascading order, when 2 css rules have the same media, same importance, same origin and same specificity, then the declarations of the last css rule must prevail: (...) if two declarations have the same weight, origin and specificity, the latter specified wins
. Firefox 1.5, Firefox 2.x, Safari 2.0.4, Safari 3.0.4, Opera 9.25, Opera 9.50, Konqueror 3.5.8, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, NS 7.0, NS 7.2, Galeon 2, Epiphany 2 all pass this test.
42- Top and bottom borders not rendered. Internet Explorer 6, Firefox 1.5, Firefox 2.x, Safari 2.0.4, Safari 3.0.4, Opera 9.25, Opera 9.50, Konqueror 3.5.8, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, NS 7.0, NS 7.2, Galeon 2, Epiphany 2 all pass this test.
43- Padding and border are rendered beneath body node. Since the blue-bordered inline-elements seem to have a lower stacking position than the red bordered body node in Internet Explorer 7 and Internet Explorer 8, then the border and padding areas are not visible, not viewable, seem to be truncated. This is most likely the same bug as the Disappearing border-top bug reported by Ben Hollis and the same bug that is affecting this 1997 Web Standards Project basic testcase. Firefox 1.x, Firefox 2.x, Safari 2.0.4, Safari 3.0.4, Opera 9.25, Opera 9.50, Konqueror 3.5.8, Hv3 TKHTML alpha 16, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, NS 6.2, NS 7.0, NS 7.2, Galeon 2, Epiphany 2 all pass this test.
CSS 2.1, Section 9.9.1 states
"Each stacking context consists of the following stacking levels (from back to front):
1. the background and borders of the element forming the stacking context.
2. the stacking contexts of descendants with negative stack levels.
3. a stacking level containing in-flow non-inline-level descendants.
4. a stacking level for floats and their contents.
5. a stacking level for in-flow inline-level descendants. (...)"
CSS 2.1, Section 9.9.1 Layered presentation; Specifying the stack level: the 'z-index' property
This testcase is actually rendered worse in Internet Explorer 8 as the left padding area is not reactive on an hovering of the mouse.
44- Caption box should be rendered outside of table box: Caption box should be rendered outside of table box when border-collapse value is separate, Internet Explorer 8 renders the caption box inside (not outside) the table box. Internet Explorer 7, Firefox 2, Firefox 3, Opera 9.x, Safari 3, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, NS 7.x, Galeon 2.14, Epiphany 2.20, Hv3 TKHTML alpha 16 all pass this test.
45- Text selection is weird, sometimes difficult, often inaccurate. Here's the latest discovery with text selection. Visit this advanced layout 5 with floats by Gabriele Romanato and then (steps to reproduce) select/highlight the words "Site.com" and (actual results) you'll see the horse background-image (expected results) when you should not.
46- Text underlining is not always redrawn when scrolling. This seems to be a regression.
47- Image inside label with for not reacting as expected Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.0.4, Safari 3.1, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.0.4, Konqueror 3.5.8, 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.
48- Top and bottom margins unexpectedly not rendered in Internet Explorer 8; 1st additional testcase: bottom margin not rendered, 2nd additional testcase: bottom margin not rendered. Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.0, NS 7.2, K-meleon 1.x, Konqueror 3.5.8, Epiphany 2.22, Galeon 2.0.4, Hv3 TKHTML alpha 16, Amaya 10.0 build 20080229 all pass these 3 testcases. Credit must go to Dorayme for posting this issue in comp.infosystems.www.authoring.stylesheets forum discussion newsgroup the IE 7 Margin Problem message and for his No Expected margin bottom in IE 7 testcase.
49- Archive webstandards.org testcase still not passed after 11 years!. For various reasons, every single version of IE fails to pass this testcase: that's over 11 years! In IE 8 beta 1, the padding area of the inline element is incorrectly painted. A white strip on top of the words appears when aqua color should be painted uniformly.
50- Nested Q element (nested short quotations) incorrectly rendered in Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 beta 1: this testcase directly comes from the HTML 4.01 example of nested quotations with the Q element from HTML 4.01, section 9.2.2 example on Rendering nested quotations. This absence of support has also been explained and testcase-ed by Aaron Gustafson in his Support Q in IE.next Wishlist. Firefox 2.x, Firefox 3, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.22, Galeon 2.0.4 all pass this test.
51-60 10 testcases from Ian "Hixie" Hickson evil testsuite still fail in IE 8 beta 1. Those 10 testcases had been explicitly reported already back in september 2006 and have been published more than 6 years ago:
| link to actual test page | IE 7 | IE 8 b1 | Firefox 1.5 | Opera 9 | Other browsers which pass the test page | |
|---|---|---|---|---|---|---|
| link to actual test page | IE 7 | IE 8 b1 | Firefox 1.5 | Opera 9 | Other browsers which pass the test page | |
| 51 | Shorthand border property | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0, Amaya 9.53 |
| 52 | At-rules | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0 |
| 53 | :visited link | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0 |
| 54 | Dynamic pseudo-class :focus | Fails | Fails | Passes | ?Passes? | |
| 55 | DOM mutation on :hover effect | Fails | Fails | Passes | Fails | |
| 56 | border-width-right | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0 |
| 57 | thin bottom border | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0, Amaya 9.54 |
| 58 | thin left border | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0, Amaya 9.54 |
| 59 | border-width | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0, Amaya 9.5 |
| 60 | border-color | Fails | Fails | Passes | Passes | NS 6.2, NS 7.0 |
61- DOM 3 Core textContent support. Firefox 1.5, Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.22, Galeon 2.0.4 all pass this test.
62- Closing non-script-initiated single-tab windows and tab instances According to MSDN2, non-script-initiated single-tab windows and tab instances should not be able to be closed by javascript without a prompt confirmation window. 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.
63- Padding values are not applied to HTML document root element Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.22, Galeon 2.0.4 all pass this test. This bug has also been reported by Mark "Tarquin" Wilton-Jones in his Padding on the HTML element is ignored demo and by James Hopkins in his IE8 Beta 1 Regression Bug: specifying a padding value on html demo.
64- Border values are not applied to HTML document root element Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Epiphany 2.22, Galeon 2.0.4 all pass this test.
65- 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.
66- getAttribute("style") on an element returns an object in Internet Explorer, not a string When querying getAttribute("style") on a node, Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 beta 1 return an object and not a string. This bug is also reported by Peter-Paul Koch in his DOM compatibility table for attributes on getAttribute() and by many web authors. 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.
67- Table cells should expand vertically to fill a table height if required. CSS 2.1, section 17.5.3 Table height algorithms states that Cell boxes that are smaller than the height of the row receive extra top or bottom padding.
Internet Explorer 6, Internet Explorer 7, Firefox 1.5, Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 2.0.4, 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 is a regression.
68- Counting nested tables with a counter fails Internet Explorer 8 beta 1 counts 12(!) nested tables when there are only 4. Firefox 2.x, Firefox 3, Opera 9.26, Opera 9.50, Safari 3.1, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test.
69- 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, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass this test. This is a regression.
70- Activating form controls thanks to implicit labels and accesskey fails. Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 beta 1 fail 8 tests out of 10. Firefox 2.x, Firefox 3, Opera 9.26 (fails 3 tests out of 10), Opera 9.50, Safari 3.1, Konqueror 3.5.8, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass these 10 tests.
71- Margin-bottom of child in overflowed block is not rendered This is clearly a spec violation regarding CSS 2.1, section 10.6.3. Firefox 2.x and Internet Explorer 7 pass both tests.
72- Dynamically adding <option>s into a select with DOM 1/2 HTML add() method is broken in Internet Explorer. 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, Epiphany 2 all pass this test. This bug has been reported at connect's IE beta feedback as bug 338795.
73- Top: auto offset miscalculation in Internet Explorer 8 beta 1. Internet Explorer 7, Firefox 2, Firefox 3, Opera 9.27, Opera 9.50, Safari 3.1, Seamonkey 2.x, NS 7.2 all pass this test.
74- An unclosed <p> immediately preceding a form element should be implicitly closed by IE when parsing and building DOM tree. Firefox 2.0.0.13, Opera 9.27, Opera 9.50, Safari 3.1, Konqueror 3.5.8, 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.
75- Support for <option disabled> in Internet Explorer. Lack of support for <option disabled> in a select (drop-down list) has been mentioned, explained, utterly documented, testcase-ed by many in all kinds of forums, webpages, public lists of bugs, web authoring forum discussions over the last 5 years. Firefox 1.5, Firefox 2, Firefox 3, Opera 9.27, Opera 9.50, Safari 3.1, Seamonkey 1.x, Seamonkey 2.x, NS 7.0, NS 7.2, K-meleon 1.x, Galeon 2 and Epiphany 2 all pass this test. This bug has been reported at connect's IE beta feedback as bug 336685 This bug has been closed by the IE team and will not be fixed for the release of IE 8 final.
76- Absolutely positioned box that is a child of a relatively positioned box is mispositioned: the CSS 2.1, section 9.8.4 example. This first test comes directly from CSS 2.1, section 9.8.4. There is also another abs. pos. box child of a rel. pos. box test, a demo for CSS tooltip, which IE 8 beta 1 fails. Firefox 2, Firefox 3, Opera 9.27, Opera 9.50, Safari 2.0.4, Safari 3.1.1, Seamonkey 1.x, Seamonkey 2.x, K-meleon 1.x, Galeon 2.0.4, Epiphany 2.22 all pass these 2 tests. Konqueror 3.5.8 passes the 2nd test. This bug has been reported at connect's IE beta feedback as bug 338788.
77- @import-ing a style sheet for "print" fails in IE 7 and in IE 8 beta 1. 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.
78- Hovering floated links makes adjacent sibling move up and down (1st test). 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.
79- Hovering floated links makes adjacent sibling move up and down (2nd test). 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.
