Change Details

== Plan (YMMV) * Check if the original bug affects Grade A browsers. ** If it doesn't, remove the `readonly` attribute and take it easy for the rest of the day. ** If it does, then: * T161763#3162791? --- When covering over the search field (before clicking on it), the cursor does not in any way reveal that there is a clickable area. At first I thought the mouse events were hijacked due to the presence of `div.transparent-shield.cloaked-element` (which would be addressed by setting `pointer-events: none;` so that hover and focus events will go through to the underlying elements instead). However, that was a red herring. It seems the real culprit is the presence of a `readonly` attribute on the input field. Why is this there?

When covering over the search field on tablet/desktop (before clicking on it), the cursor does not in any way reveal that there is a clickable area. At first I thought the mouse events were hijacked due to the presence of `div.transparent-shield.cloaked-element` (which would be addressed by setting `pointer-events: none;` so that hover and focus events will go through to the underlying elements instead). However, that was a red herring. It seems the real culprit is the presence of a `readonly` attribute on the input field. Why is this there? == Plan (YMMV) * Check if the original bug affects Grade A browsers. ** If it doesn't, remove the `readonly` attribute and take it easy for the rest of the day. ** If it does, then: * T161763#3162791? ---

When covering over the search field on tablet/desktop (before clicking on it), the cursor does not in any way reveal that there is a clickable area. At first I thought the mouse events were hijacked due to the presence of `div.transparent-shield.cloaked-element` (which would be addressed by setting `pointer-events: none;` so that hover and focus events will go through to the underlying elements instead). However, that was a red herring. It seems the real culprit is the presence of a `readonly` attribute on the input field. Why is this there? == Plan (YMMV) * Check if the original bug affects Grade A browsers. ** If it doesn't, remove the `readonly` attribute and take it easy for the rest of the day. ** If it does, then: * T161763#3162791? --- When covering over the search field (before clicking on it), the cursor does not in any way reveal that there is a clickable area. At first I thought the mouse events were hijacked due to the presence of `div.transparent-shield.cloaked-element` (which would be addressed by setting `pointer-events: none;` so that hover and focus events will go through to the underlying elements instead). However, that was a red herring. It seems the real culprit is the presence of a `readonly` attribute on the input field. Why is this there?