Hi,
Sorry that we were looking at the client side behavior. eo_Callback does trigger server side validation logic. Server side validation logic is triggered by ASP.NET when it can not find a "source control" that can be "responsible" for the postback (when it can find a "responsible" control, it lets that control to decide). When you use a trigger, the triggering control is regarded as "responsible", however when you use eo_Callback on another server control, it's hard to say whether the control or the CallbackPanel is responsible, so nobody is actually regarded responsible in this case.
One of the reasons that we decided not to have a CausesValidation on the CallbackPanel was that when you use a trigger, it's the triggering control's CausesValidation that should be honored, the CallbackPanel supposes to be transparent. So having a CausesValidation on the CallbackPanel would just confuse user at this case.
In order to avoid the problem, you can override Page.Validate function. You can do something like:
Code: C#
public override void Validate()
{
if (!callbackPanel.IsCallback)
base.Validate();
}
That should skip validation when it's a callback.
Thanks