469,950 Members | 2,369 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,950 developers. It's quick & easy.

Disable Combo Items


How to disable combo items?

Mervin Jadhav
Software Developer
Solutiioneyes Pvt Ltd (http://www.solutiioneyes.com)
203, Sai Chambers, 16 Mumbai-Pune Rd, Pune - 411 003 INDIA
me**********@yahoo.com
Voice: + 91 20 2553 9120 | fax: +91 20 2553 5293 | +91 20 9890921356

--
MervinJadhav
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------

Dec 9 '05 #1
3 2014
MervinJadhav wrote:
How to disable combo items?


For the most part, this is not really an ASP issue. But here are some
suggestions, assuming you mean HTML SELECT elements, not "combo items":

Don't use them
Toggle the [disabled] property
Set the DISABLED attribute
Omit the NAME attribute
Ignore its value on the server side

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.
Dec 9 '05 #2
Dave Anderson wrote:
MervinJadhav wrote:
How to disable combo items?


For the most part, this is not really an ASP issue. But here are some
suggestions, assuming you mean HTML SELECT elements, not "combo
items":
Don't use them


Huh? That's a new one. What is your objection to using SELECT elements and
what's the alternative?
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
Dec 9 '05 #3
Bob Barrows [MVP] wrote:
Don't use them


Huh? That's a new one. What is your objection to using SELECT
elements and what's the alternative?


I have no objection to SELECT elements. Not using them happens to be one way
to avoid giving the client access to them.

I am a client-side-security atheist, and whenever I see a question like
this, I suspect a well-meaning but useless "security" effort. If the point
of "disabling" is to improve some logic flow or otherwise enhance the UI,
fine. But what's the point in putting all of those OPTIONS on the page if
you don't want the user to have access to them? In many such cases, simply
not using a SELECT element would be a better design choice.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.
Dec 9 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Bob Bedford | last post: by
2 posts views Thread by Nikolay Petrov | last post: by
2 posts views Thread by http://www.visual-basic-data-mining.net/forum | last post: by
2 posts views Thread by Dave | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.