Hyperlinks inside AutoHideArea sometimes doesn't work

3 posts, 1 answers
  1. BENN
    BENN avatar
    59 posts
    Member since:
    Dec 2011

    Posted 01 Feb Link to this post

    if you click it, then you might see that the AutoHideArea stays open and the hyperlink works.

    However, if you hide the autohide by clicking on another pane, and then hovering on the autohide pane header (so it will open), and click on the hyperlink, then there is a good chance that the autohide area will code immediately, and that the hyperlink will not execute.


    I have traced this issue to be a focus issue, and I have "fixed" it by registering to a mouse down (or preview mouse down) on the hyperlink, and then setting focus on the first focusable ancestor.


  2. Answer
    Nasko avatar
    587 posts

    Posted 02 Feb Link to this post

    Hello Benn,

    The observed by you behavior is caused by the current implementation of the control. Let me explain why exactly that behavior occurs. When you click the Pane it is actually activated and when you hover over the Pane that has Hyperlink placed inside it the clicked Pane remains the active one. So, when you click the hyperlink the active pane is deactivated and the OnPaneDeactivated logic of our built-in FlyoutBehavior is called. Inside it we have an implemented logic to check if the current selected Pane is active (in this case this is the pane with the hyperlink) and if it is not active to close it.

    So, the approach you found seems an appropriate one to move the focus to the current selected Pane. However, as another approach that we could suggest you is to modify the default FlyoutBehavior of RadDocking and more specifically the logic implemented inside the OnPaneDeactivated method. You could do that by creating a class that inherits the IFlyoutBehavior interface. We have created a sample project that demonstrates that - please, notice that the implementation is a sample one and you might need to improve it in order to make the behavior of the AutoHideArea worked as expected.

    We hope this will help you.

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for WPF is Visual Studio 2017 Ready
  4. BENN
    BENN avatar
    59 posts
    Member since:
    Dec 2011

    Posted 03 Feb in reply to Nasko Link to this post

    Thanks :-)
Back to Top