Hi Michela,

I have good news that we found a solution for the reported case. Please put the following raiseEvent function override above the RadEditor declaration and let me know the result.

        <script>
            Telerik.Web.UI.EditorButton.prototype.raiseEvent = function (eventName, eventArgs) {
                var handler = this.get_events().getHandler(eventName);

                if (handler) {
                    if (!eventArgs) {
                        eventArgs = new Sys.EventArgs();
                    }

                    handler(this, eventArgs);
                }
            }
            function OnClientCommandExecuting(editor, args) {

                alert(args.get_value());

            }
    </script>
    <telerik:RadEditor RenderMode="Lightweight" runat="server" ID="RadEditor1" Height="600px" OnClientCommandExecuting="OnClientCommandExecuting">

Regards,
Rumen
Progress Telerik

Hi Michela,

Thank you for the additional details!

I've reproduced the issue and converted the support ticket into a public bug report so the community is aware. I'll need a bit more time to investigate whether there's a reliable workaround, and I'll share any findings here.

As a small token of appreciation for your valuable feedback, I've also updated your Telerik points.

Regards,
Rumen
Progress Telerik

Hi Michela,

Thank you for the detailed report and the screenshot.

From what you've described and based on the image you shared, it looks like the problem is related to an incorrect args object being passed to the OnClientCommandExecuting event handler of the RadEditor. The problem looks similar to the one discussed in this KB article: args.get_name is not a function when executing the OnClientCommandExecuting event.

In particular, the args you're receiving in certain cases appears to be a TreeListDataItem, rather than the expected EditorCommandEventArgs. This can result in errors like:

Uncaught TypeError: args.get_commandName is not a function

To resolve this, we recommend updating your event handler to include a type check before attempting to access the properties or methods on the args object. For example:

<script>
    function OnClientCommandExecuting(editor, args) {
        debugger;
        if (!args || !args.get_commandName || typeof args.get_commandName !== "function") return;

        var name = args.get_name();
        var val = args.get_value();
        var cArea = editor.get_contentArea();
        var selectedElement = editor.getSelectedElement();
    }
</script>

This approach ensures that the handler only runs when the correct args object is present, preventing the type error and allowing your toolbar functionality (like changing the background color) to work reliably.

Please try implementing the solution and let us know if the issue persists or if you need further assistance. We're happy to help!

Regards,
Rumen
Progress Telerik