Input fields give interactability cues even though "readonly" flag is set

[ViliusBa]

Using an input field <Input> and passing readonly flag as true disallows editing of the field which is expected. However, it still gives off misleading hints of being editable by having an outline focus on click and the change of cursor on hover. Was this intended?

[FlyersPh9]

This is working as originally intended, see the 3rd example on this page. The text field should still be focusable so keyboard users can access it, and the user should be able to click into it to highlight the text for copy / paste. The only difference should be the lack of typing / deleting the text.

[mayank99]

Generally speaking, readonly inputs should be avoided exactly for reasons like this one.

If you want to display values that cannot be edited, consider using static text instead of an <Input>. For creating a list of static label/value pairs, you might find the <dl> element useful.