W3C home > Mailing lists > Public > www-validator@w3.org > December 2015

Re: bug

From: Michael[tm] Smith <mike@w3.org>
Date: Sun, 27 Dec 2015 11:20:49 +0900
To: leandro pacheco <leandrozpacheco@gmail.com>
Cc: www-validator@w3.org
Message-ID: <20151227022049.GT25514@sideshowbarker.net>
"Michael[tm] Smith" <mike@w3.org>, 2015-12-27 10:12 +0900:
> Archived-At: <http://www.w3.org/mid/20151227011247.GS25514@sideshowbarker.net>
> leandro pacheco <leandrozpacheco@gmail.com>, 2015-12-25 22:07 -0200:
> > Archived-At: <http://www.w3.org/mid/CAMjdwfEDzhcBh-vT=0UF_HY2hJTO5Oh-1HZcymjfhrauC7jSBg@mail.gmail.com>
> > 
> > bug: https://i.gyazo.com/c89b323f2156926e0866ed2c4e9a5e54.png
> Thanks for reporting this. You caught a parsing regression I inadvertently
> introduced recently around the error reporting behavior for ampersand
> characters. I’ll get it fixed soon but in the mean time time, you can work
> around it by replacing the ampersand in line 154 of your frameB.html source
> file with “&amp;”; like this:
>   <a href=”http://photorack.net/index.php?action=showgal&amp;cat=1">

I believe I’ve now fixed the parser regression and if you re-check your
document with <a href="http://photorack.net/index.php?action=showgal&cat=1">
as is (that is, without needing to change the ampersand to “&amp;” you
should find that it proceeds without hitting that internal error.

Thanks again for catching this. If you run into further “internal error”
failures or otherwise notice odd error-reporting around ampersands, please
do take time again to report them.


Michael[tm] Smith https://people.w3.org/mike

Received on Sunday, 27 December 2015 02:21:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:18:14 UTC