J
Juan T. Llibre
re:
You will have to live with, and die by, JavaScript, then.
re:
But, it does work, as long as you identify the browser
and send it HTML/scripts it understands.
The whole "I shouldn't have to code" idea is just lazyness, to me.
I'm not saying that it should be harder/more complicated than
it needs to be, but requiring "no code" is just absurd.
That's how we make a living : by writing code!
Get used to it...or go to a different platform.
Then you''ll see what complex, *really hard to grasp* code is.
All I care is Java Script is universal
You will have to live with, and die by, JavaScript, then.
re:
then it should also work with the simple "required field" validator component and I
should not have to code browsercaps mess.
But, it does work, as long as you identify the browser
and send it HTML/scripts it understands.
The whole "I shouldn't have to code" idea is just lazyness, to me.
I'm not saying that it should be harder/more complicated than
it needs to be, but requiring "no code" is just absurd.
That's how we make a living : by writing code!
Get used to it...or go to a different platform.
Then you''ll see what complex, *really hard to grasp* code is.
4WJ said:All I care is Java Script is universal, and it has been working on most modern browsers
that the current market offers. If it fails to validate a simple "required field"
request on the client browser, then it is broken, incompatible, considered as a bug,
monopoly, you name it. On top of that, if the same page can implement onBlur and onFocus
events using the same script engine, then it should also work with the simple "required
field" validator component and I should not have to code browsercaps mess.
Why does it work on one and not the others ? Are Asp.Net Required Field Validators using
different JS engine than onBlur, onFocus, onDoubleClick...? Why should I have to
remember which one requires browsercap settings. That's bad design my friend! NO GOOD!!!
John