hmmm.... this is a tricky one. A script is being executed during parsing
and the document is basically getting deleted while it is running. What
we would need here is some way to stop the script from running when we
go to a new URL - but I'm guessing this is difficult while we are in a
function called from the script?
A quick-fix in for this particular case could be to get it to set
executingScript to false before it goes to the new URL. But that
basically defeats the purpose of the assert, and it is not a good
long-term solution because we still have to work out how to stop scripts
that are running when the URL changes. I'm sure there are many other
situations in which this could be a problem.
Harri Porten wrote:
>
> Hi !
>
> I just looked at
>
> http://bugs.kde.org//db/83/8302.html
>
> and stripped it down to
>
>
>
>
>
>
>
>
> This triggers assert(executingScript == false); in
> KHTMLTokenizer::reset() Waldo put in. It surely is there for a reason
> but what's the proper fix ? reset() is being called in
> ~KHTMLTokenizer(). Can anyone (Waldo? Peter?) shed light on this issue ?
>
> Thanks,
>
> Harri.
--
Peter Kelly
pmk@post.com