Reset checkbutton problem

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 2
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
  • RobG
    #16
    Re: Reset checkbutton problem

    On Jan 17, 10:01 am, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
    wrote:
    RobG wrote:
    On Jan 17, 9:26 am, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
    wrote:
    RobG wrote:
    >On Jan 17, 4:00 am, David Mark <dmark.cins...@ gmail.comwrote:
    >>On Jan 16, 10:07 am, GArlington <garling...@tis cali.co.ukwrote :
    >>>On Jan 16, 2:20 pm, Giovanni D'Ascola <giovanni.dasc. ..@gmail.cm>
    >>>wrote:
    >>>>Giovanni D'Ascola ha scritto:Hi.
    >>>>>I noticed that <input type="reset"act ually don't enable checkbutton
    >>>>>which are checked by default after they have been disabled by
    >>>>>javascript . It's a bug?
    >>>>The browser is Mozilla Firefox.
    >>>This behaviour is exhibited by IE6 too... Both are NOT reseting the
    >>>value of disabled attribute.
    >>Another good reason to forget about reset buttons. They are worse
    >>than useless.
    >I don't think so - most forms should have a reset button, perhaps
    >labelled "Cancel", unless there is a very good reason not to have one.
    Would this suffice? http://www.useit.com/alertbox/20000416.html
    >
    No.
    >
    That is one person's opinion and is based on a number of spurious
    assertions from a particular point of view. [...]
    >
    You might want to check the background of the author before making *your*
    spurious assertions. Jakob Nielsen certainly is not just anyone.
    He certainly isn't, but for the article to be taken at anything other
    than face value, references need to be provided where assertions are
    made.

    Statements like:

    "The Web is characterized by frequent movement between pages and users
    rarely encounter the same form twice."

    indicate that Jakob's context is a general user on the web, but there
    are many other contexts - e.g. business applications (regardless of
    whether it is web-based or not). In that case, users frequently visit
    the same form - some will nearly always have data already in them and
    others only sometimes. It is not reasonable to characterise the
    entire gamut of user interface design from a single perspective.

    If you wish to use Jakob's work to support your case (which is quite
    reasonable) you should find an article written in an appropriate
    context, or make your own arguments based on references to his work.


    --
    Rob

      Comment

      • David Mark
        #17
        Re: Reset checkbutton problem

        On Jan 16, 7:08 pm, Giovanni D'Ascola <giovanni.dasc. ..@gmail.cm>
        wrote:
        David Mark ha scritto:
        >
        >
        >
        On Jan 16, 6:17 pm, RobG <rg...@iinet.ne t.auwrote:
        On Jan 17, 4:00 am, David Mark <dmark.cins...@ gmail.comwrote:
        >
        >On Jan 16, 10:07 am, GArlington <garling...@tis cali.co.ukwrote :
        >>On Jan 16, 2:20 pm, Giovanni D'Ascola <giovanni.dasc. ..@gmail.cm>
        >>wrote:
        >>>Giovanni D'Ascola ha scritto:Hi.
        >>>>I noticed that <input type="reset"act ually don't enable checkbutton
        >>>>which are checked by default after they have been disabled by
        >>>>javascrip t. It's a bug?
        >>>The browser is Mozilla Firefox.
        >>This behaviour is exhibited by IE6 too... Both are NOT reseting the
        >>value of disabled attribute.
        >Another good reason to forget about reset buttons.  They are worse
        >than useless.
        I don't think so - most forms should have a reset button, perhaps
        >
        Why?  Of all of the dialogs I have ever designed (or seen for that
        matter), I can't think of one that had a reset button.
        >
        labelled "Cancel", unless there is a very good reason not to have one.
        >
        Not Cancel.  A cancel button is typically used to redirect back to the
        page that initiated the dialog (or hide it if it was displayed via
        Ajax.)  I think Reset is the only option, unless the form is always
        initially empty, in which case Clear would be appropriate.
        >
        If a script messes around with a form so that the reset button no
        longer works correctly, that is the fault of the script, not the reset
        >
        It is the fault of browser developers if it fails to reset values of
        disabled elements, though I don't think that a reset button should
        have any effect on their disabled states (oddly enough it seems it
        affects only some types of inputs.)  If you must have a reset and you
        dynamically disable elements, then you have to have a click handler on
        the button to adjust the states accordingly.
        >
        button.  It is quite reasonable for the OP to want to maintain a
        consistent operation of the reset button.
        >
        Certainly.  The question is whether the application really needs a
        reset button, especially considering the headaches that go along with
        one.
        >
        The reset button, imho, is useful when a form is filled with a large
        number of default values. If you modify them, then you can restore them
        simply by clicking on the reset button.
        What would be the point of that? If it is a form that edits
        previously entered data, then it would reset to whatever was entered
        by the user during the last editing session. It is a sort of
        primitive (and destructive) undo.

        For entering new data, it is clearly worthless.

          Comment

          Previous 1 2 template Next
          Working...