Projects/KHTML - Revision history

Vtokarev at 19:33, 19 November 2008

2008-11-19T19:33:20Z

Tampakrap at 22:29, 18 November 2008

2008-11-18T22:29:10Z

SadEagle: /* Potentially high-impact bugs */

2008-10-20T16:14:17Z

‎Potentially high-impact bugs

Tampakrap at 15:29, 13 October 2008

2008-10-13T15:29:45Z

Vtokarev: /* Major targets */

2008-10-10T07:49:44Z

‎Major targets

Vtokarev: /* Major targets */

2008-10-10T07:49:18Z

‎Major targets

Tampakrap at 13:31, 9 October 2008

2008-10-09T13:31:28Z

Tampakrap at 13:23, 9 October 2008

2008-10-09T13:23:06Z

Tampakrap at 14:54, 4 October 2008

2008-10-04T14:54:14Z

SadEagle: /* In-progress bugfixes */

2008-10-03T00:30:48Z

‎In-progress bugfixes

@@ Line 23: / Line 23: @@
 === 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}} ?
 === Acid3 stuff ===
@@ Line 27: / Line 24: @@
 === Potentially high-impact bugs ===
 * {{Bug|150662}}
-* {{Bug|158532}} --- assert failure in the outline painting code. Didn't manage to sort it out myself - S.E.
 * 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 27: / Line 27: @@
 === 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.

@@ 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}} ?
 * I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086
@@ Line 33: / Line 30: @@
 * 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.

@@ Line 15: / Line 15: @@
 * SVG --- vtokarev
 * DOM namespace changes --- vtokarev --- done (in trunk)
-* Class attribute hashconsing for improved css selectors performance
+* 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

@@ Line 1: / Line 1: @@
 === In-progress bugfixes ===
 * SadEagle:{{Bug|169988}} --- focus/blur on all elements, head/body parsing #?????, multiple problems with onchange ({{Bug|170451}}, many others)
-* RTL application (-reverse) fixes
+** head/body parsing : {{Bug|170694}} ?
-* make frame resizing dynamical - possibly with a frame indicator.
+* Spart: RTL application (-reverse) fixes
-* need to add/update several testcases in regression suite for 4 or 5 five bug fixes (Sp.)
+* Spart: make frame resizing dynamical - possibly with a frame indicator.
 * I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086

@@ Line 1: / Line 1: @@
 === In-progress bugfixes ===
 * SadEagle:{{Bug|169988}} --- focus/blur on all elements, head/body parsing #?????, multiple problems with onchange ({{Bug|170451}}, many others)
-** onchange on lineedit/textarea isn't called because handleFocusOut isn't called for redirected widgets
+* RTL application (-reverse) fixes
-*** would something like http://rafb.net/p/ikWvHK97.html do? I didn't actually tested the patch for lack of a testcase though.(Sp.)
+* make frame resizing dynamical - possibly with a frame indicator.
-****seem to work fine so I'll go ahead... (Sp.)
-* working on integrating changes in 4.1.2 ChangeLog (Sp.)
-** Woops, done that already. Sorry. -Maks.
-*** bah, nevermind... I'm too slow. Thank you.(Sp.)
 * need to add/update several testcases in regression suite for 4 or 5 five bug fixes (Sp.)
-* I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086 , however I'm not sure what's the policy for sharing of private interfaces between sub directories of kdelibs... may I just #include <kio/hostinfo_p.h> or should this interface be made public first?  (Sp.)
+* I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086
-** At the very least it'd need to have the class exported via the KIO_EXPORT macro
+** 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 31: / Line 27: @@
 === 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.):
 ** 1. Go to http://www.cs.cornell.edu/courses/cs3810/2008fa/
@@ Line 42: / Line 35: @@
 ** 3. Scroll down.
 ** 4. Click on Grading/HW again -- much of the frame isn't repainted

← Older revision		Revision as of 00:30, 3 October 2008
Line 10:		Line 10:

	* I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086 , however I'm not sure what's the policy for sharing of private interfaces between sub directories of kdelibs... may I just #include <kio/hostinfo_p.h> or should this interface be made public first? (Sp.)		* I have a patch for doing dns-prefetch as was suggested on http://www.kdedevelopers.org/node/3701#comment-8086 , however I'm not sure what's the policy for sharing of private interfaces between sub directories of kdelibs... may I just #include <kio/hostinfo_p.h> or should this interface be made public first? (Sp.)
		+	** At the very least it'd need to have the class exported via the KIO_EXPORT macro

	=== Acid3 stuff ===		=== Acid3 stuff ===