Le Mon, 06 Mar 2006 16:25:12 +0200, Mikko Rantalainen
[EMAIL PROTECTED] a écrit:
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
ROBO Design wrote:
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.
Maybe adding an attribute for this sole purpose is too
Quoting ROBO Design [EMAIL PROTECTED]:
...
form action=order_place.asp
input type=submit value=PLACE ORDER
input type=submit value=SAVE QUOTE action=quote_add.asp#thanks
input type=submit value=RECALCULATE TOTALS action=#here
/form
What's wrong with using the form attribute to point to
Anne van Kesteren wrote:
Quoting ROBO Design [EMAIL PROTECTED]:
...
form action=order_place.asp
input type=submit value=PLACE ORDER
input type=submit value=SAVE QUOTE action=quote_add.asp#thanks
input type=submit value=RECALCULATE TOTALS action=#here
/form
What's wrong with using the form
Anne van Kesteren wrote:
Quoting ROBO Design [EMAIL PROTECTED]:
...
form action=order_place.asp
input type=submit value=PLACE ORDER
input type=submit value=SAVE QUOTE action=quote_add.asp#thanks
input type=submit value=RECALCULATE TOTALS action=#here
/form
What's wrong with using the form
On Mon, 6 Mar 2006, Mikko Rantalainen wrote:
Perhaps something along the lines
form action=url
input name=foo type=submit anchor=xfoo
input name=bar type=submit anchor=xbar
/form
With WF2 you can just do:
form action=url
input name=foo type=submit action=url#xfoo
input
Mikko Rantalainen wrote:
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
Some comments on section 1.8, Conformance requirements in the
2006-02-16 draft of Web Applications 1.0 (whose permanent URL claims to
be http://www.whatwg.org/specs/web-apps/current-work/ ).
The opening sentence:
As well as sections marked as non-normative, all diagrams, examples,
and notes
I'd like to see a little more information in the Status of this
Document section of Web Applications 1.0. In particular:
* Are there large sections likely to appear in the document in the
future? If so, what? Section 1.10 (Miscellaneous) suggests that
there are. (Although I'm not sure
The following are comments on section 2.8 (Lists) of the 2006-02-16
draft of Web Applications 1.0 [1].
The text on list numbering seems to lack conformance criteria. The term
ordinal value of a list item should probably more clearly be a
definition (and not split into multiple places), and there
10 matches
Mail list logo