it seems to work if I change line 354 (ekhtml_starttag.c) to
if( *workp == '<') {
and line 329 to
for(;workp != endp && *workp != '<'; workp++){
this doesn't work with a single > in the attributes name: ">"
I didn't made any tests with < in attributes value.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No you are wrong: you say "...while forgiving syntactically
incorrect tags..."
And often in attributes there maybe Javascript just like
<a onclick="if (x>10) foo()"> and browsers just handle it.
So I think that ekhtml should just handle it too and it
doesn't matter if iit is in any specs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=811710
it seems to work if I change line 354 (ekhtml_starttag.c) to
if( *workp == '<') {
and line 329 to
for(;workp != endp && *workp != '<'; workp++){
this doesn't work with a single > in the attributes name: ">"
I didn't made any tests with < in attributes value.
Logged In: YES
user_id=17434
That isn't valid in an attribute for anything (or shouldn't be, since
the spec says so)
Try:
<a href="#" name="x-&gt;y">
Logged In: YES
user_id=811710
No you are wrong: you say "...while forgiving syntactically
incorrect tags..."
And often in attributes there maybe Javascript just like
<a onclick="if (x>10) foo()"> and browsers just handle it.
So I think that ekhtml should just handle it too and it
doesn't matter if iit is in any specs.