ComboBox Shift+Tab not working then IsEditable is True

[ghost]

Issue description

I try to make a custom ComboBox. But i have a problem with the example from this document.
The SHIFT+TAB not working then the IsEditable is True.

Target framework

• .NET Framework - 4.5.2

edit by @mairaw: added document details

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 463966c3-3bf3-d3da-418f-4756956a99c0
• Version Independent ID: 21abf0b8-13d4-f81f-fc81-09505902fd19
• Content: ComboBox Styles and Templates
• Content Source: docs/framework/wpf/controls/combobox-styles-and-templates.md
• Product: dotnet-framework
• Technology: dotnet-wpf
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[mairaw]

Thanks for your feedback @Andro-Marian. @grubioe can you please check this feedback for a WPF article?

[grubioe]

• @rladuca @vatsan-madhavan

[BionicCode]

Solution

It's required to disable the tab stop for the case that the ComboBox is in edit mode (IsEditable="True").
To avoid such situations, it's always recommended to edit a copy of the original control styles by going to the XAML design view and right-click the corresponding control and select "Edit Template | Edit a Copy..." from the context menu.
Alternatively it's possible to use Visual Studio Blend to modify the default style. The styles and templates provided on Microsoft Docs are not always accurate.

To solve the issue you should add a Trigger to the style (which is present in the original style,, when following the above steps to retrieve the control's original style):

<Style x:Key="{x:Type ComboBox}"
       TargetType="{x:Type ComboBox}">

  ...

  <Style.Triggers>
    <Trigger Property="IsEditable" Value="true">
      <Setter Property="IsTabStop" Value="false" />
    </Trigger>
  </Style.Triggers>
</Style>

[rladuca]

@fabiant3 @SamBent @ryalanms We were tagged on this a while back, but I don't have any insight into how this bug came about. Tagging you to notify you of this one.

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.