Projects/KHTML: Difference between revisions

Latest revision as of 19:33, 19 November 2008

In-progress bugfixes

SadEagle:bug #169988 --- focus/blur on all elements, head/body parsing #?????, multiple problems with onchange (bug #170451, many others)
- head/body parsing : bug #170694 ?

Acid3 stuff

See Projects/Acid3

Major targets

SVG --- vtokarev
DOM namespace changes --- vtokarev --- done (in trunk)
Class attribute hashconsing for improved css selectors performance --- vtokarev
- Implementation that we have currently is significantly slower on specific test case (probably less on real-life pages). Anyway, it should improve performance (maybe even memory usage), with small drawback on complexity
HTML5 Audio/Video --- Spart
getComputedStyle w/display:none --- SadEagle
- Acid3 #35/#41, bug #169617
iframe stuff --- SadEagle, non-immediate
- XSS permissions for about: and javascript: URL affect tinyMCE
canvas --- SadEagle, non-immediate:
- New params to putImageData, createImageData, parameter checking updates
- Depends on getComputedStyle:
  - Add support for currentColor
  - text

Potentially high-impact bugs

derstandard.at
tokenizer script-recursion crashes - (what bug #? (Spart))
- Might not be a good name, but I mean: bug #170185, part of bug #165601, part of bug #162498, later bts and dupes of bug #145666, and likely some others. My initial description is probably wrong, though --- the problem is the hack in handling window.document that creates the document by calling begin/write/end is doing so on a document with a parser active; one of the triggers is probably because the restoration of frames from KHTMLPageCache may happen in the wrong order, but the various reports suggest it's not the only case. (The reason for the original description is that I recalled seeing quite a few reports mentioning the same m_scriptExecuting assert, e.g. bug #118104 for a long time, and figured it's time to get rid of this; some of those are actually mixed in with the dupes of the above). -S.E.
  - I analyzed this some more, and it's very hard to fix; basically the whole restoreState on multiple frames thing is broken, as it tries to restore kids independently of parents, and each may have <script> fragments, etc. The code likely needs to be reworked to do deferred application of saved info such as scroll position, etc., once loaded. -Maks

@@ Line 2: / Line 2: @@
 * SadEagle:{{Bug|169988}} --- focus/blur on all elements, head/body parsing #?????, multiple problems with onchange ({{Bug|170451}}, many others)
 ** head/body parsing : {{Bug|170694}} ?
-* Spart: RTL application (-reverse) fixes
-* Spart: make frame resizing dynamical - possibly with a frame indicator.
-* Spart: still need to add/update several testcases in regression suite for 4 or 5 five bug fixes
-* I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086
-** Maksim, to answer your question, the point is not to retrieve on hover but as soon as an anchor's href is parsed, so it is wasteful, but the Chromium guys say they observe it doesn't put a significant pressure on DNSes as the average page as few external links. My approach would be to cap the number of resolution to something (configurable) like 40 per page, getting most of the benefit on news site, without the DDOSing behaviour. It does give a kind of "what could possibly go wrong" feeling though :-)
 === Acid3 stuff ===
@@ Line 14: / Line 8: @@
 === Major targets ===
 * SVG --- vtokarev
-* DOM namespace changes --- vtokarev
+* DOM namespace changes --- vtokarev --- done (in trunk)
+* Class attribute hashconsing for improved css selectors performance --- vtokarev
+** Implementation that we have currently is significantly slower on specific test case (probably less on real-life pages). Anyway, it should improve performance (maybe even memory usage), with small drawback on complexity
 * HTML5 Audio/Video --- Spart
 * getComputedStyle w/display:none  --- SadEagle
@@ Line 27: / Line 23: @@
 === Potentially high-impact bugs ===
-* {{Bug|150662}}
 * derstandard.at
 * tokenizer script-recursion crashes - (what bug #? (Spart))
 ** Might not be a good name, but I mean: {{Bug|170185}}, part of {{Bug|165601}}, part of {{Bug|162498}}, later bts and dupes of {{Bug|145666}}, and likely some others. My initial description is probably wrong, though --- the problem is the hack in handling window.document that creates the document by calling begin/write/end is doing so on a document with a parser active; one of the triggers is probably because the restoration of frames from KHTMLPageCache may happen in the wrong order, but the various reports suggest it's not the only case. (The reason for the original description is that I recalled seeing quite a few reports mentioning the same m_scriptExecuting assert, e.g. {{Bug|118104}} for a long time, and figured it's time to get rid of this; some of those are actually mixed in with the dupes of the above). -S.E.
-* Sometimes changing pages doesn't repaint properly, leaving parts of the old one. I've seen it on lists.kde.org, but can't reproduce now , here is one reproducible (r855004 on branch)testcase, though (but this one uses frames, not standalone) (-S.E.):
+*** I analyzed this some more, and it's very hard to fix; basically the whole restoreState on multiple frames thing is broken, as it tries to restore kids independently of parents, and each may have <script> fragments, etc. The code likely needs to be reworked to do deferred application of saved info such as scroll position, etc., once loaded. -Maks
-** 1. Go to http://www.cs.cornell.edu/courses/cs3810/2008fa/
-** 2. Click on Grading/HW
-** 3. Scroll down.
-** 4. Click on Grading/HW again -- much of the frame isn't repainted
-*** fixed in my tree, thanks for the nice test case (Sp.)