Wpf tab browser control trial#

doesn't work - home and end still not working Private void MarkdownMonsterTabControl_PreviewKeyDown(object sender, KeyEventArgs e) PreviewKeyDown += MarkdownMonsterTabControl_PreviewKeyDown hook up key event rather than overriing base control Several people mentioned that overriding events should also fix the problem, but it turns out that it doesn't: protected override void OnInitialized(EventArgs e) For now this solves my problem of the missing Home and End key processing. I may have to adjust to return some functionality that I might not be aware of, or possibly may also need to add OnKeyUp() to handle additional keys etc. so I don't actually need the default behavior (and it doesn't work properly with tab re-ordering). I already have custom tab handling in place for rotating through open tabs and closing etc. If (e.Key = Key.Home || e.Key = Key.End)Īctually - that's not quite what I'm using: I actually don't call OnKeyDown() at all so I'm not letting the TabControl do any key processing (whatever that might be): protected override void OnKeyDown(KeyEventArgs e) Protected override void OnKeyDown(KeyEventArgs e) The trick is to override the base TabControl or TabablzControl control used and override the OnKeyDown handler to essentially not forward the offending keys: public class MarkdownMonsterTabControl : TabablzControl OK, so now that I know the problem, how do I fix it? Fixing the Keyboard Forwarding in the TabControl It's doubly frustrating because the WebView2 is not forwarding other keys (like Accellerator keys alt for menu and hotkey operations) that I actually would like to see forwarded. The TabControl supports turning off navigation features via Keyboard sub-properties, but those seemed to have no effect and the key forwarding happened regardless.Īlso, the behavior of WebView2 is different from the old IE based WebBrowser control which had no problem living inside of a Tab Control and was not forwarding keys.

Now it's debatable whether this behavior is correct or not. In the testing earlier, both the base TabControl and the TabablzControl exhibit the same key forwarding behavior. I am actually using a custom Tab Control - the excellent TabablzControl from the Dragablz package - but it inherits the keyboard behavior from the default WPF TabControl. But once I opened multiple tabs it became clear that the Tab Control's Tab Navigation was kicking in navigating to the first and last tab respectively rather than handling Home and End in the Editor. That's the clue - the TabControl is interfering with the WebView's keyboard handling and stealing focus from the Web Browser for tab navigation.Īt first I didn't notice the Tab navigation behavior because I only had a single tab open. If I have multiple tabs open the keys navigate to the first and last tab respectively. If I have a single tab open the keys are just dead and don't do anything.

In that scenario the Home and End key don't work inside of the control. It turns out the problem occurs when the WebView2 is hosted inside of a TabControl. The latter two scenarios point at the real problem: A WebView running inside of a TabControll Keyboard Leakage with a TabControl

Testing Editor Container inside of Tab Container (doesn't work - Aha!).

Testing WebView inside of Tab Container (doesn't work - Aha!).

Testing adding my Editor Container into standalone form (works).

Testing as runtime added UserControl (works).

Testing in a standalone WPF Window (works!).

Remove all key handlers in JavaScript (doesn't work).

Wpf tab browser control trial#

It took a few hours for me to track the Home and End key non-workage down through a bunch trial and error tests with the WebView control. But once I started cleaning up my async errors and got the control to run, the problem unfortunately persisted. Since I just managed to get the control running and there were still a lot of errors from the interop calls into the control I figured it was probably due to some key processing in the control. All other keys and key combos seem to be fine and enter or navigate in the editor, but very specifically Home and End do not work! Troubleshooting Keyboard Handling - Ugh! The keys do not work in the editor - initially they did nothing. One of these 'Side Effects' is: When I first got the WebView2 running with the HTML based editor, I noticed that the Home and End keys were not working. It has turned into a much bigger job than I wanted it to be due to the async requirements for JavaScript interop resulting in the dreaded Async Application Cascade, but also - and more importantly for this post - a few unexpected Side Effects. I've been slowly pushing through my WebView2 conversion of the Markdown Monster Editor component from the old Web Browser control.