Re[2]: WF2, abolish <button type=remove>

Good day, Josh.

JS> An analogous suggestion would be to move form reset and submit buttons
JS> into the browser.

JS> add/remove as well as reset/submit

This in not analogous seggestion - it's necessary to rank buttons:
(1) form contains one submit- and one reset-button,
(2) repetation block contains one add-button
    (but form can contains several and even nested repetation blocks,
    thus form contains _several_ add-button),
(3) copy of repeated block contains one remove-button
    (but repetation block can consist of several copies,
    thus repetation block contain several remove-button,
    and form contains __several-in-square__ remove-button).

I take _not_ arbitrary case (as you thought), but polar case.
You try to refuse my proposal by bringing example from _opposite_ pole
- that is not correct from point of logic.

Ranking show,
that necessity to abolish is different to different buttons.

JS> if multiple forms are present on the page,
JS> it's more clear to have each control co-located with its form.

It's disputable question, what is more clear:
co-located control or button in browser itself.
But what is definitely,
that quantity of remove-buttons grows in _geometrical progression_ and
make documents bulky.



Dmitry Turin
http://html6.by.ru
http://sql4.by.ru
http://computer2.by.ru

Received on Thursday, 31 May 2007 08:02:14 UTC