Difference between revisions of "Projects/Acid3"

Jump to: navigation, search
(add column indicating if test passes in ff3b5 or not)
Line 9: Line 9:
 
! Diagnosis
 
! Diagnosis
 
! Comment
 
! Comment
 +
! passes in FF3b5
 
|-
 
|-
| 04 || HTML Parser || Parser bug: iframe missing text kid || discard_until = ID_IFRAME+ID_CLOSE_TAG --- added in http://lists.kde.org/?l=kde-commits&m=99906936412933&w=2.  
+
| 04 || HTML Parser || Parser bug: iframe missing text kid || discard_until = ID_IFRAME+ID_CLOSE_TAG --- added in http://lists.kde.org/?l=kde-commits&m=99906936412933&w=2. || No
 
|-
 
|-
| 13 || DOM Range || Unhandled mutation ||
+
| 13 || DOM Range || Unhandled mutation || || Yes
 
|-
 
|-
| 18 || ???? || ???? ||
+
| 18 || ???? || ???? || || Yes
 
|-
 
|-
| Red image(16) || Part loading || Not doing fall-back content || ... when no mimetype specified (WIP)
+
| Red image(16) || Part loading || Not doing fall-back content || ... when no mimetype specified (WIP) || Yes
 
|-
 
|-
| 26/27 || JS + DOM Memory management || Cycle breaking cleaning up too much ||  
+
| 26/27 || JS + DOM Memory management || Cycle breaking cleaning up too much || || Yes, but slow
 
|-
 
|-
| 29 || HTML Parser || Parser bug: table missing whitespace kid ||  
+
| 29 || HTML Parser || Parser bug: table missing whitespace kid || || Yes
 
|-
 
|-
| 35 || CSS ||  getComputedStyle() on <head> (no renderer) ||
+
| 35 || CSS ||  getComputedStyle() on <head> (no renderer) || || Yes
 
|-
 
|-
| 38 || CSS || Lack of restyle || "adding text to a text node didn't make the element non-:empty"
+
| 38 || CSS || Lack of restyle || "adding text to a text node didn't make the element non-:empty" || No
 
|-
 
|-
| 41 || CSS ||  getComputedStyle() on something else rendererless ||
+
| 41 || CSS ||  getComputedStyle() on something else rendererless || || Yes
 
|-
 
|-
| 43 ||  ||  || Checkboxes, value, attributes
+
| 43 ||  ||  || Checkboxes, value, attributes || Yes
 
|-
 
|-
| 44 || ????|| ???? ||  
+
| 44 || ????|| ???? || || Yes
 
|-
 
|-
| 48 (red linktest failed) || CSS || :visited doesn't match relative URL right || Performance critical, hot on things like Qt docs, and already slow
+
| 48 (red linktest failed) || CSS || :visited doesn't match relative URL right || Performance critical, hot on things like Qt docs, and already slow || Yes
 
|-
 
|-
| 51 || DOM2 Table || Stray row || Buggy test. Raised with Ian Hickson.
+
| 51 || DOM2 Table || Stray row || Buggy test. Raised with Ian Hickson. || Yes
 
|-
 
|-
| 53 || DOM2 Forms || Not managing form's element collection when not in document. ||
+
| 53 || DOM2 Forms || Not managing form's element collection when not in document. || || Yes
 
|-
 
|-
| 65/69 || Part loading || onload events not emitted for many objects ||
+
| 65/69 || Part loading || onload events not emitted for many objects || || Yes, after several attempts
 
|-
 
|-
| 70-80 || || Can't run due to 65/69 || SVG, SMIL + XHTML
+
| 70-80 || || Can't run due to 65/69 || SVG, SMIL + XHTML || No
 
|-
 
|-
| 89 || JS RegExp || Lacking syntax check || Perl-centric PCRE behavior. Contacted author.
+
| 89 || JS RegExp || Lacking syntax check || Perl-centric PCRE behavior. Contacted author. || Yes
 
|-
 
|-
 
| 90 || JS RegExp || References || Perl-centric PCRE behavior. Contacted author.  
 
| 90 || JS RegExp || References || Perl-centric PCRE behavior. Contacted author.  
 
(was it ever considered to use Boost.Regex engine instead ? it claims to be using strict ECMA syntax as per http://boost.org/doc/libs/1_35_0/libs/regex/doc/html/boost_regex/ref/syntax_option_type/syntax_option_type_perl.html
 
(was it ever considered to use Boost.Regex engine instead ? it claims to be using strict ECMA syntax as per http://boost.org/doc/libs/1_35_0/libs/regex/doc/html/boost_regex/ref/syntax_option_type/syntax_option_type_perl.html
  
Update: I tried to build a test application with Boost.Regex 1.33 and it had the same issues than PCRE: /a[])]/ compiled and /(\3)(\1)(a)/ went back as "Invalid Back Reference". -gg
+
Update: I tried to build a test application with Boost.Regex 1.33 and it had the same issues than PCRE: /a[])]/ compiled and /(\3)(\1)(a)/ went back as "Invalid Back Reference". -gg  
  
 
Seems that despite the name, it's not really ES compatible --- if the docs are right, it doesn't support \u.
 
Seems that despite the name, it's not really ES compatible --- if the docs are right, it doesn't support \u.
)
+
  || Yes
 
|-
 
|-
| 98 || XHTML || createDocument() || Not reparenting doctype, not creating XHTML document
+
| 98 || XHTML || createDocument() || Not reparenting doctype, not creating XHTML document || No
 
|}
 
|}

Revision as of 23:24, 5 April 2008

Acid3 Test Failures of KHTML

This is an overview of the remaing failures of KHTML on the Acid3 test.

Test No Area Diagnosis Comment passes in FF3b5
04 HTML Parser Parser bug: iframe missing text kid discard_until = ID_IFRAME+ID_CLOSE_TAG --- added in http://lists.kde.org/?l=kde-commits&m=99906936412933&w=2. No
13 DOM Range Unhandled mutation Yes
18  ????  ???? Yes
Red image(16) Part loading Not doing fall-back content ... when no mimetype specified (WIP) Yes
26/27 JS + DOM Memory management Cycle breaking cleaning up too much Yes, but slow
29 HTML Parser Parser bug: table missing whitespace kid Yes
35 CSS getComputedStyle() on <head> (no renderer) Yes
38 CSS Lack of restyle "adding text to a text node didn't make the element non-:empty" No
41 CSS getComputedStyle() on something else rendererless Yes
43 Checkboxes, value, attributes Yes
44  ????  ???? Yes
48 (red linktest failed) CSS  :visited doesn't match relative URL right Performance critical, hot on things like Qt docs, and already slow Yes
51 DOM2 Table Stray row Buggy test. Raised with Ian Hickson. Yes
53 DOM2 Forms Not managing form's element collection when not in document. Yes
65/69 Part loading onload events not emitted for many objects Yes, after several attempts
70-80 Can't run due to 65/69 SVG, SMIL + XHTML No
89 JS RegExp Lacking syntax check Perl-centric PCRE behavior. Contacted author. Yes
90 JS RegExp References Perl-centric PCRE behavior. Contacted author.

(was it ever considered to use Boost.Regex engine instead ? it claims to be using strict ECMA syntax as per http://boost.org/doc/libs/1_35_0/libs/regex/doc/html/boost_regex/ref/syntax_option_type/syntax_option_type_perl.html

Update: I tried to build a test application with Boost.Regex 1.33 and it had the same issues than PCRE: /a[])]/ compiled and /(\3)(\1)(a)/ went back as "Invalid Back Reference". -gg

Seems that despite the name, it's not really ES compatible --- if the docs are right, it doesn't support \u.

Yes
98 XHTML createDocument() Not reparenting doctype, not creating XHTML document No

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal