Hi Christian,

Yes, it is possible as of version 4.4. I confirm that your observations are completely correct.

Here is a base example:

<TelerikTextBox Placeholder="test content" Width="180px" ReadOnly="true" />

Regards,
Hristian Stefanov
Progress Telerik

Hi Smiljan,

I want to express my heartfelt appreciation for your extraordinary patience during the course of my investigations. The duration of the process exceeded our initial expectations due to certain internal factors, such as extensive discussions within our team and a significant workload in recent weeks.

Now I'm finally able to share news on this item.

I want to assure you that the work on the implementation of the feature has already begun. Our team has dedicated efforts toward its development, and we anticipate its inclusion in one of our upcoming releases. As soon as we have a definitive timeline, the status of this item will be updated to "Planned," along with the expected completion date.

Regards,
Hristian Stefanov
Progress Telerik

Hi Smiljan,

Thank you for bringing this to our attention.

Indeed, the feature is highly requested. It seems to have somehow slipped out of our planning.

I will reach out to our management to determine the appropriate future release for incorporating the feature, taking into consideration our capacity.

I will get back here with new updates very soon.

Regards,
Hristian Stefanov
Progress Telerik

Hello,

To get updates when something happens (say, a release number is known), click the Follow button on the portal page.

Regards,
Marin Bratanov
Progress Telerik

Hello Tony,

The HTML editor is not a plain input, and disabling it is supposed to disable interaction with the content. If you want to keep interaction, I recommend using an if-block to either render the editor, or the HTML string that it would otherwise work with.

Regards,
Marin Bratanov
Progress Telerik

Hi Tony,

I updated the opener post with a few more selectors that target date inputs and dropdownlists.

The pattern here is that you need to find the input whose pointer-events CSS rule you need to set to initial so that selection can happen. You can do that by inspecting the rendered HTML to see what selector you need for the particular case.

Regards,
Marin Bratanov
Progress Telerik

Hi all,

I've edited the opener post to add a workaround you can consider for the time being.

Regards,
Marin Bratanov
Progress Telerik

Hi Scott,

I renamed this feature request to better reflect your goal - I don't find it likely that it would be solved through a readonly attribute, though.

What I can suggest at this point is that you consider an if-else block instead of the Editable parameter - if the field is to be editable, render an enabled input, if not - render plain text without a component and inputs.

Regards,
Marin Bratanov
Progress Telerik

Hello Scott,

With simple inputs, I can copy from both disabled and readonly text

<input disabled value="I am disabled" />
<br /><br />
<input readonly value="I am read-only" />

Thus, the rules we have for disabled inputs are a bonus that is not solved by adding a readonly attribute.

The k-textbox class has a cascade that sets pointer-events: none for disabled inputs, but not for readonly inputs, hence the difference - I cannot copy from the disabled one defined like this:

<input disabled value="I am disabled" class="k-textbox" />
<br /><br />
<input readonly value="I am read-only" class="k-textbox" />

Disabling the pointer events on a readonly input has different behavior than on a disabled one, and that's something the browser controls, you can test it without any Telerik code like this:

<input disabled value="I am disabled" class="custom-class" />
<br /><br />
<input readonly value="I am read-only" class="custom-class" />

<style>
    .custom-class[readonly] {
        pointer-events: none;
        border: 1px solid red;
    }
</style>

With regards to your second paragraph - I am not sure I understand the goal in relation to the original request. Do you want the user to be able to copy text from a disabled input? My initial understanding was that you do not, and that matches the behavior we have.

Regards,
Marin Bratanov
Progress Telerik

Hello Scott,

The disabled CSS class we add to the rendering of disabled components sets the pointer-events rule to "none" for the inputs, which disables selection and thus - copying. Can you show me how you can copy from a disabled input of ours?

On a side note - when you have sent information to the user, they can copy it anyway - both in Server-side blazor (e.g., by extracting it from the DOM), and for WebAssembly (where it often also arrives as a REST HTTP call response).

Regards,
Marin Bratanov
Progress Telerik