The site contains a text-area in a form which is in a table. The source code of the table row with the text-area is <tr> <td>Anfrage</td> <td><textarea name="anfrage" cols="40" rows="10"</textarea></td> </tr> and doesn't cause problems with the stable version of Safari 5 nor with Gecko browsers I tested so far. However, WebKit r61670 stops displaying to another div that should be shown (div id="menu" which is shown if you are logged in). For some reason it fills code into the textarea. This is not intended in the source code, however, the web inspector clearly shows that it's just put into there. The code in question is everything that comes after </textarea>, causing, for example, div="menu" which is specified after </textarea> not to appear. WebKit r61670 on Mac OS X 10.6, problem not appearing in the stable version of Safari 5.
<textarea name="anfrage" cols="40" rows="10"</textarea> Yep. The problem is the missing ">" on the textarea start tag.
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=9985
(In reply to comment #1) > <textarea name="anfrage" cols="40" rows="10"</textarea> > > Yep. The problem is the missing ">" on the textarea start tag. I see, so the parsing behaviour changed in the nightlies. Thanks! I will, of course, correct that mistake in the site - just saying because you linked that site as an example at w3.org. Should I upload the broken site elsewhere so you can use that example further? Funny that nobody who checked the source code (including me) noticed that so that I filed a bug, though.
> I see, so the parsing behaviour changed in the nightlies. Thanks! Yeah, we're implementing the HTML5 parsing algorithm. > I will, of course, correct that mistake in the site - just saying because you linked that site as an example at w3.org. Should I upload the broken site elsewhere so you can use that example further? That's not really necessary. We know that problem is. The tricky part is that the new behavior matches Internet Explorer, so your site is/was probably broken in IE. It's unclear whether more web sites are broken with the old behavior or the new behavior. > Funny that nobody who checked the source code (including me) noticed that so that I filed a bug, though. Thanks for filing the bug. It helps us get a sense for how many sites are affected by the change. It's a tough typo to spot. We've been pouring over these details recently, so it's something we're used to looking for this week. :)
It appears that the site is fixed now. Thanks for updating it.
Marking as a duplicate of Bug 40961 so we can track how often these issue occur. *** This bug has been marked as a duplicate of bug 40961 ***