Hi Richard,
I think that you guessed the issue correctly.
The content of the Firefox memory contains HTML that is transformed a little
because of several reasons like javascript execution and as you can see
there are
several HTML errors in it. The one you saw is just a example of one,
there is another
one with & in the arguments of urls. I should log a Firefox bug on this.
But I found
no time to do it yet.
Marc
Richard de Boer wrote:
> Hello Marc,
>
> First of all, let me thank you for creating your validator extension,
> I'm using it all the time and it is much easier to use then using online
> validators all the time.
>
> I'm currently using the beta version (HTML Validator 0.8.3 on Firefox
> 1.5.0.4), and although mostly it works fine, there seems to be a bug in
> the validation after javascript execution:
> The page I'm validating (www.stchristoffel.nl , Dutch) is written in
> XHTML 1.0 Transitional, so all empty tags like <br /> have to be ended
> with a slash. When using the normal validation everything works fine,
> but when validating after javascript all those tags have their slashes
> stripped: <br /> becomes <br>, <img src="blah" /> becomes <img
> src="blah"> etc. This even happens when javascript is turned off.
> After that both Tidy and the SGML parser do their job, so they give
> warnings/errors for all those tags.
> I suppose this is probably (still) a bug in the way Firefox passes the
> page source along, but I thought I'd let you know anyway.
>
> I tried to use the logging as described on
> http://users.skynet.be/mgueury/mozilla/faq.html#DIAGLOG , but it didn't
> seem to work: I set 'tidy.options.diaglog_dir' to 'c:\tiylog' and
> 'tidy.options.debug' to true and restarted Firefox, but after validating
> no logs were created. I'm guessing it might not be enabled in the beta
> version yet, but if I did anything wrong I'd be happy to try again.
>
>
> Keep up the good work,
>
> Richard de Boer
>
>
>
|
