RE: [NUnitAsp-devl] Allowing Enable Property to Be Set

[Aaron J. <aj...@pr...>]

Jim Shore wrote:
> 1- I have been considering removing the 'enabled' assertion entirely.
> The method would still be present but NUnitAsp would stop throwing
> exceptions when a control is disabled.  I would still include your
> patch, as I think it has broader uses.  Do you think removing the
> 'enabled' assertion would be a good idea?  Why/why not? (Anybody else
> with an opinion on this, feel free to chime in.)

I like the assertion, as it mimics real UI usage.  The user "throws an
exception" when he tries to work with a disabled control, and makes him
do something to enable the control.

Essentially, leaving the assertion in forces testers to mimic the same
work as their JavaScript.  For example, in my control, I have two radio
buttons and two checkboxes.  By default, the checkboxes are disabled
until the second radio button is checked.  In my tester for this
control, when I set the Checked property on the radio buttons, I also
enable/disable the checkboxes as needed.

Does that make sense?


> 2- I see that you don't allow the 'id' attribute to be changed.  What
> was the reasoning behind that?

I did not know if this would cause Very Bad Things(tm) to happen in the
rest of NUnitAsp, i.e., I did not know if it assumed IDs are static and
never changed. I figured it was better to be safe than sorry.  If you do
not think it necessary, by all means, remove.

Let me know if you have any more questions.

     <:> Aaron