PostBackUrl Changes on All Buttons

I have a very strange problem here.  There is a page with an ImageButton displayed inside a user control (ascx file).  This ImageButton only needs to perform JavaScript, so I disabled the postback by setting postbackurl to "javascript:void(0);".  After I click on this ImageButton, though, the postbackUrl on all the other Asp buttons also become "javascript:void(0);".  I can see it when I hover over them in IE.   So, my Asp:buttons are essentially then disabled.

Is this normal?  I don't change the postBackUrl on an object very often.  But is it supposed to make it change on all the other buttons?  Before I click on the first button, the other Asp buttons work fine and execute their postback instructions.  Only after clicking on the first button does the postBackUrl change.  I know it's not the fault of the javaScipt instructions I'm calling because it happens even after it is commented out.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

all you have to do is set the OnClientClick proprty dont change de postpackurl property...

OnClientClick="youJsFunction();return false;"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dparkesAuthor Commented:
I tried that and it did not work.  Seems like all the rules change now that the button is in a user control.  
I think I've fixed it by explicitly setting the postbackurl parameter in the buttons.    
dparkesAuthor Commented:
Ah yes, this was right.  I had other conflicting code that was masking this issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.