On Mon, Oct 13, 2008 at 05:06:23PM +0000, corvid wrote:
Francis wrote:
On Fri, Oct 10, 2008 at 12:43:59PM +0000, corvid wrote:
Christopher wrote:
Doing web searches using www.altavista.com does not work. It is as if the search terms are not submitted.
Searching for "Images", "MP3/Audio", or "Video" instead of "Web" or "News" works well.
It's a problem with altavista, in that their HTML is invalid, and therefore they rely on browser-fixups to get the result they probably wanted.
It's a problem with dillo, in that the submit button (presumably) works for most other browsers.
More specifically, the main difference between the (working) images page and the (failing) web page is the presence of an explicit close-table-cell </td> tag.
If you remove the </td> on line 68 of the altavista index.html page, then the submit button works.
So presumably dillo is handling "explicit </td> before <td>" differently from "no </td> immediately before <td>", at least in this case.
I think dillo sees <td> ... <form> ... </td> and closes the form, which seems like the right behavior.
Yes; it is "a" right behaviour. Because the markup is incorrect, pretty much anything dillo does is right. But what dillo does, is it sees <table><tr><td><form><input></td><td> and (correctly) closes the form when it sees "</td>". And on the "images" search page, dillo sees the (I think) exactly equivalent <table><tr><td><form><input><tr> and (also correctly) does not close the form when it sees "<tr>" which implies "</td>" and "</tr>". That was the difference I was trying to point out. The html is broken in each case. Dillo's handling of it is valid in each case. But the second example results in "friendlier" response to the user (in this case. Under other circumstances, showing the brokenness may be "friendlier"). f -- Francis Daly francis@daoine.org