Revert :read-only selector back to [readonly]

[mdo]

Reverts #33642. Fixes #33860, fixes #33925.

[arcanisgk]

why isn't there a design difference between read-only and disabled?

The difference between disabled and readonly is that read-only controls can still function and are still focusable, whereas disabled controls can not receive focus and are not submitted with the form and generally do not function as controls until they are enabled.

The idea of using bootstrap is that the designs of the web pages are similar and in the best of cases that the elements are intuitive; so being an end user and seeing a disabled or read-only field, I'm not getting any visual feedback...

would it be possible to use a specific pointer for each type of situation?

for example field disabled can use cursor: not-allowed;

for example field read-only i have not find a default cursor, and cant find any related icon in BS ICON but i search in other solution and find one that i can use in a custom from FontAwesome:

for example font awesome have this icon:

in the end I was hoping that this could be fixed within BS as part of its visual aid to the end user.

[mdo]

@arcanisgk Please don't add unrelated comments to closed pull requests. You won't likely get a reply from anyone. This was also addressed to an extent in #36499 and will ship soon.