Hi - this one is a feature request, not a bug. :)

For the filter menu, when you enter a filter value, it would be nice if you could press enter to execute the filter instead of having to click "Filter."

I want a less-persistent popup, where a click outside of its boundaries would close it. To give a real world example, the Share Snippet feature in REPL works in such a way.

===

Telerik edit: A workaround for the time being is to attach a JavaScript click handler that closes the Popup instance:  https://blazorrepl.telerik.com/GyumGrEs22yZgoCD16 

The behavior is reproducible only in the Material and Bootstrap themes - it can be observed in the online demo.

When I scroll to a point where an appointment is not fully visible and click it, the page scrolls up. This does not happen in the other themes.

Reproduction video: https://www.loom.com/share/b8303675096d42ea8582a1638f37571f.

Hello, 

We are looking to port an angularjs web application to Blazor and I didn't see the diagram component similar to the one found in Kendo UI. It would be nice to see a viso-like component in UI for Blazor.

Thank you.

We upgraded to the latest Telerik Blazor components (8.1.1).
I think there's a bug in the TabStrip when setting the index of the ActiveTabIndex or @bind-ActiveTabIndex.
The page will scroll to the active tab automatically.

Here's a link to the Repl - https://blazorrepl.telerik.com/GfaTEmbR45zQSzEq44

If you remove @bind-ActiveTabIndex="@ActiveTabIndex" from the TelerikTabStrip then the page load normally.

Thanks,

Cesar

On the Spreadsheet control please display a function list when the user types "=" or provide the user with some other reference about the available functions.

• Spreadsheet function dropdown in KendoReact
• Spreadsheet function dropdown in Kendo Angular

After filtering a nullable int column, the SelectAll checkbox in the GridCheckboxColumn stops working.

Reproduction example: https://blazorrepl.telerik.com/mTuyHaYM44sLH2yf05

Hello,

Please consider a Grid feature that changes the component layout on mobile devices or narrow screens. The idea is to switch the column layout to a card layout or anything similar to this example: https://css-tricks.com/responsive-data-tables/

It is possible to implement a similar behavior with the Telerik Blazor Grid and MediaQuery components, but it requires reusing the column titles in the CSS code: https://blazorrepl.telerik.com/GnYPmHFR176Jg5Yg02

===

Telerik Blazor team: Everyone who is interested in this feature, please vote for it to help us prioritize. Also, share your opinion about which Grid features you strictly need in the "mobile" layout and which ones you are ready to sacrifice. Some features don't make sense in a card / listview layout anyway, but still, the mobile-friendly Grid may require completely different HTML markup and UX, so some features may need to be completely revamped.

I want to use the built-in FileManagerToolBarSortTool but I want to remove the "Date Modified" option from the "Sort BY" menu.

===

ADMIN EDIT

===

For the time being, a possible option is to create a custom tool for sorting. You can use the SplitButton component to simulate the built-in UI. Upon selecting option from the dropdown, you may sort your data collection based on the selected custom sort option. Call the Rebind method to refresh the data after updating it.

In the Appearance section of the ContextMenu component documentation on the Progress Design System Kit website (https://www.telerik.com/design-system/docs/components/contextmenu/#size), it is stated that:

The ContextMenu provides the size configuration option that enables you to control how big or small the rendered submenu items in the popup will be.

I’ve observed that this functionality is implemented in at least one library—Kendo UI for Angular (https://www.telerik.com/kendo-angular-ui/components/menus/contextmenu/appearance#size).

Is there a plan to introduce support for the Size parameter in the ContextMenu component of the Telerik UI for Blazor library?

We have forms that starts with single text box input, all other inputs are either hidden or disabled. Based on the value of that input we load additional data from the server, show/enable the rest of the inputs and move the focus to the next unput. We react to the value in that first input either when the Enter key is pressed, or when the input loses focus e.g. tab-out of the input or click/tap on another input. One or the other but never both. This scenario should be handled by the OnChange event. However, the OnChange event fires twice, when the enter key is pressed and again when the text box loses focus. This results in double data retrieval (takes twice the time), screen flicker and creates unpleasant user experience.

The recommended workaround is to add second variable to track if the input actually changed and ignore consequent events for the same value. This has it’s own caveat. If for any reason the user wants to retrieve the related data from server again e.g. he was notified it has changed, then he cannot use the OnChange event anymore because the value hasn’t changed and the event will be ignored. So the user has to change the value twice.

 We found a second workaround, see code below. Blur the text box on enter and handle only the on OnBlur event to process the value. This way we can process the value repeatedly, the user presses enter or tab-out, then focus back on the same input and hit enter or tab-out and repeat as many times as desired.

 We propose OnEnter event to be added to the text box so we don’t have to handle @onkeypress on outer <div>. The <div> events are also not synchronized with the DebounceDelay parameter of the text box. We have to either set the DebounceDelay to 0 or introduce delay in the KeyHandler method. The text box has OnBlur event already but surprisingly there is no OnEnter event.

We also proposed BlurAsync() method that will eliminate the need to create the javascript function and invoke JSRuntime.

 <<< javascript function >>>
function blurInput(inputId) {
    const textField = document.getElementById(inputId);
    if (textField) {
        textField.blur();
    }
}

<<< Blazor >>>
@page "/" 
@inject IJSRuntime JSRuntime

<PageTitle>Home</PageTitle>

<div @onkeydown="@(async (args) => await KeyHandler(args))">
    <TelerikTextBox id="txt1" Width="20rem" Placeholder="Pallet" DebounceDelay="0" @bind-Value="@_textInput" OnBlur="@OnInputBlur" />
</div>
<div>
    <TelerikTextBox @ref="_txtRef" Width="20rem" Placeholder="Pallet" />
</div>

@code
{
    private string? _textInput;
    private TelerikTextBox _txtRef = null!;

    private async Task KeyHandler(KeyboardEventArgs e)
    {
        if (e.Key == "Enter")
        {
            await JSRuntime.InvokeVoidAsync("blurInput", "txt1");
        }
    }

    private async Task OnInputBlur()
    {
        Console.WriteLine($"Bound variable: {_textInput}");
        await _txtRef.FocusAsync();
    }
}

}

When unpinning a DockManager pane, the unpinned pane always collapses to the left. Need the ability to configure it to collapse to the right or top instead.

In the meantime, a possible alternative to position it to the right is to override the default theme styles with the following CSS approach:

<style>
    .unpin-to-right {
        display: flex;
        flex-direction: row-reverse;
    }
</style>

<TelerikDockManager Height="90vh" Class="unpin-to-right">
    <DockManagerPanes>

        <DockManagerSplitPane Orientation="@DockManagerPaneOrientation.Vertical"
                              Size="40%">
            <Panes>

                <DockManagerContentPane Size="55%" HeaderText="Pane 1.1">
                    <Content>
                        First Content Pane in Split configuration
                    </Content>
                </DockManagerContentPane>

                <DockManagerContentPane HeaderText="Pane 1.2">
                    <Content>
                        Second Content Pane in Split configuration
                    </Content>
                </DockManagerContentPane>

            </Panes>
        </DockManagerSplitPane>

        <DockManagerTabGroupPane>
            <Panes>

                <DockManagerContentPane HeaderText="Tab 2.1">
                    <Content>
                        First Tab Content
                    </Content>
                </DockManagerContentPane>

                <DockManagerContentPane HeaderText="Tab 2.2">
                    <Content>
                        Second Tab Content
                    </Content>
                </DockManagerContentPane>

            </Panes>
        </DockManagerTabGroupPane>
    </DockManagerPanes>

    <DockManagerFloatingPanes>
        <DockManagerSplitPane>
            <Panes>

                <DockManagerContentPane HeaderText="Floating Pane">
                    <Content>
                        Floating Pane Content
                    </Content>
                </DockManagerContentPane>

            </Panes>
        </DockManagerSplitPane>
    </DockManagerFloatingPanes>
</TelerikDockManager>