Currently it's possible to do stuff like this
<form action="url#anchor">
<input name="foo" type="submit">
<input name="bar" type="submit">
</form>
and the UA scrolls down to element with id "anchor" on the page
returned by the server. It would be nice to be able to set target
anchor on per-submit-button basis.
Perhaps something along the lines
<form action="url">
<input name="foo" type="submit" anchor="xfoo">
<input name="bar" type="submit" anchor="xbar">
</form>
would result to action urls "url#xfoo" and "url#xbar" respectively.
Perhaps even if the above example had action="url#xzoo", in which
case the new anchor attribute would override the fallback behavior.
Is it too much to add a new attribute for something like this?
Note that the server cannot see any of these anchor urls. Only the
UA is able to scroll to correct position after receiving output from
the server.
--
Mikko
