Report a Silverlight Bug

Re: RC0 Error: TextBox is locked and does not fire event

StefanWick — Sat, 18 Oct 2008 15:16:13 GMT

Can you explain the scenario that this breaks? Does deriving your own class from TextBox not un-break it for you?

Thanks, Stefan Wick

Re: RC0 Error: TextBox is locked and does not fire event

mr.saif — Sat, 18 Oct 2008 12:09:17 GMT

But this breaks things for my project.....:(

Re: RC0 Error: TextBox is locked and does not fire event

StefanWick — Thu, 02 Oct 2008 05:54:09 GMT

It is consistent (I assume you are referring to the fact that the Border doesn't handle the events). Here is why:

The Border is a different element in the TextBox's tree. It doesn't take any action when you hit it with a mouse. It does not handle the input, thus it doesn't mark the event as handled, so that others can handle it further up the chain. The input area of the TextBox does take an action when you hit it with a mouse. It does handle the input, thus it marks the event as handled.

Aside from being consistent, this is also compatible with WPF, which has been using the same design and has had the same consistent behavior for years.

Thanks, Stefan Wick

Re: RC0 Error: TextBox is locked and does not fire event

stefan.josten — Thu, 02 Oct 2008 05:37:55 GMT

I disagree that this is consistent. In my opinion it's not consistent when the event is sometimes handled by the control and sometimes not.

I wanted to use this event to clear the Text in a TextBox, when the user clicks inside the Box. Your solution or using the GotFocus event works fine for me.

Thanks,

Re: RC0 Error: TextBox is locked and does not fire event

StefanWick — Thu, 02 Oct 2008 05:17:50 GMT

It actually is consistent. Further down in the reference topic there is an "Important Note" that talks about this.

http://msdn.microsoft.com/en-us/library/system.windows.uielement.mouseleftbuttondown(VS.95).aspx

"Certain control classes (for example Button) provide control-specific handling for mouse events such as MouseLeftButtonDown. The control-specific handling typically involves handling the event at a class level rather than at the instance level, and marking the MouseLeftButtonDown event data's Handled value as true such that the event cannot be handled by instances of the control class, nor by other objects anywhere further along the event route. In the case of Button, the class design does this so that the Click event can be raised instead."

This is exactly what happens here in the TextBox case. The TextBox control marks the events as handled. As I pointed out before, derived classes do receive the events - and they can set the Handled property back to false, then the mouse up/down events will fire on TextBox control. Here is how you do this:

public class TextBox2 : TextBox
{
    protected override void OnMouseLeftButtonDown(MouseButtonEventArgs e)
    {
        base.OnMouseLeftButtonDown(e);
        e.Handled = false;
    }

    protected override void OnMouseLeftButtonUp(MouseButtonEventArgs e)
    {
        base.OnMouseLeftButtonUp(e);
        e.Handled = false;
    }
}

Thanks, Stefan Wick

Re: RC0 Error: TextBox is locked and does not fire event

dbaechtel — Thu, 02 Oct 2008 00:59:23 GMT

StefanWick:

This is by design and consistent with the behavior in WPF. The TextBox marks the mouse down/up events as handled and thus won't bubble them up any further.

Thanks, Stefan Wick

Your explanation is not consistent with the online Silverlight Reference documentation on TextBox MouseLeftButtonDown event :

The MouseLeftButtonDown event is raised when the left mouse button is pressed while the mouse pointer is over the UIElement. When the mouse button is released, the MouseLeftButtonUp event is raised. However, if the mouse pointer is moved over another object when the button is released, the UIElement that received theMouseLeftButtonDown event will not receive the MouseLeftButtonUp event. There is no discrete double-click event. A double-click consists of two sequences of MouseLeftButtonDown and MouseLeftButtonUp events.

The MouseLeftButtonDown event is a bubbling event. This means that if multiple MouseLeftButtonDown event handlers are registered for a sequence of objects connected by parent-child relationships in the object tree, the event is received by each object in that relationship. The event is raised by the object that directly receives the input condition that initiates the event, and then bubbles to each successive parent object. The bubbling metaphor indicates that the event starts at the bottom and works its way up the object tree. For a bubbling event, the sender available to the event handler identifies the object where the event is handled, not necessarily the object that actually received the input condition that initiated the event. To get the object that initiated the event, use the Source value of the event's RoutedEventArgs event data.

Re: RC0 Error: TextBox is locked and does not fire event

StefanWick — Wed, 01 Oct 2008 23:16:01 GMT

This is by design and consistent with the behavior in WPF. The TextBox marks the mouse down/up events as handled and thus won't bubble them up any further.

You can get the mouse events by deriving from TextBox like this:

public class TextBox2 : TextBox
{
    protected override void OnMouseLeftButtonDown(MouseButtonEventArgs e)
    {
        base.OnMouseLeftButtonDown(e);
    }

    protected override void OnMouseLeftButtonUp(MouseButtonEventArgs e)
    {
        base.OnMouseLeftButtonUp(e);
    }
}

Thanks, Stefan Wick

Re: RC0 Error: TextBox is locked and does not fire event

dbaechtel — Wed, 01 Oct 2008 21:34:11 GMT

I agree. As long as the cursor is an Insert Cursor (I-beam), the MouseLeftButtonDown or MouseLeftButtonUp events do not fire. If you move to the border of the TextBox where the cursor changes back to the standard selection arrow, the MouseLeftButtonDown event fires and the Sender value sent to the event handler is TextBox.

This doesn't seem like it is working properly.

Re: RC0 Error: TextBox is locked and does not fire event

sebschmitt — Wed, 01 Oct 2008 14:25:41 GMT

Thanks a lot to Stefan, who already reproduced the second error.

However, I was not able to reproduce the first error, since it did not occur in any new Silverlight project I created. The App where it occurs is a bit complex , so it might take some time to find the cause. In the meantime I am happy with my workaround.

The first error however might be severe, if it really affects all Silverlight user controls in RC0.

Is it really an error caused by the release of RC0? If so, will it be fixed?

Re: RC0 Error: TextBox is locked and does not fire event

stefan.josten — Tue, 30 Sep 2008 11:34:33 GMT

Hi,

I can reprocuce the second error:

The MouseLeftButtonDown event doesn't fire, if the TextBox contains Text. Clicking near the TextBox Border (mouse icon: Arrow) works fine. Clicking inside the TextBox (mouse icon has changed) fails.

Re: RC0 Error: TextBox is locked and does not fire MouseLeftButtonDown event

Allen Chen – MSFT — Tue, 30 Sep 2008 06:22:25 GMT

Hi,

I cannot reproduce this problem. Could you post a demo project that can reproduce this problem?

Re: RC0 Error: TextBox is locked and does not fire MouseLeftButtonDown event

sebschmitt — Sun, 28 Sep 2008 13:21:46 GMT

Update: It seems like the MouseLeftButtonDown event is not fired by the Button user controls either. Maybe all user controls are affected?

RC0 Error: TextBox is locked and does not fire MouseLeftButtonDown event

sebschmitt — Sun, 28 Sep 2008 09:49:02 GMT

During my migration to RC0 I discovered a strange new behaviour of the TextBox user control:

Whenever I set its visibility attribute to "collapsed" and "visible" again, the text content is locked, meaning the user cannot change it any longer. I found a workaround by removing the text box from the children collection of its parent element and adding it again.
The MouseLeftButtonDown (defined within XAML) doesn't fire any longer without throwing any error / exception. I found a workaround by replacing this event with a GotFocus event.

Has anybody an idea, why this strange new behaviour occurs and how it might be fixed in other ways than I did?