Button events inside split button do not fire when ClosePopupOnMouseDownDelay = 0

[TAlecksen]

I have a button within a Split Button that has an event to open a Window. Since I would like the Split Button menu to close immediately after clicking the button, I have set the delay to 0 as shown below. However, the event never fires. When I set the delay to 50, it sometimes fires, and when it is 100 or greater, it always fires.

<Fluent:SplitButton ClosePopupOnMouseDown="True" ClosePopupOnMouseDownDelay="0">
  <Grid>
    <Button Click="button_Click">   
        .......
    </Button>
  </Grid>
</Fluent:SplitButton>

---

Visual Studio 2022

• Fluent.Ribbon 11.0.0
• Windows 10
• .NET 7.0

[TAlecksen]

Thank you for looking into this bug. I had one related question - Is there any way to incorporate the changes you have made through GitHub? Alternatively, do you have an estimate of when the next release will be that will incorporate this change?

[batzen]

I just release a new preview version (11.0.0-alpha0287)
Not sure about a release date for the final version of 11.0.

[TAlecksen]

Thank you! I just updated to 11.0.0-alpha0287 and am still not getting the button fire when using a ClosePopupOnMouseDownDelay = 0. Is there something different I need to do to make this work?

[batzen]

It worked in all cases i tried.
Could you provide a small repro?

[TAlecksen]

Here is a very basic setup I am using:

  <Fluent:SplitButton ClosePopupOnMouseDown="True" ClosePopupOnMouseDownDelay="0" Name="testButton" Header="Test Drop Down">
      <Button x:Name="dropdownButton" Width="30" Height="30" Click="dropdownButton_Click" />
  </Fluent:SplitButton>

    private void dropdownButton_Click(object sender, RoutedEventArgs e)
    {
        MessageBox.Show("Clicked");
    }

It works when the delay is set to 100, but not when it is 0. Please let me know if I am doing something wrong. Thank you greatly for your help.

[batzen]

I now enforce a minimum of 100 ms.
I absolutely don't understand why it worked on my machine a few days ago when enforcing 1 ms. Today it doesn't...