IOS 26 Safari: anyone else having trouble editing text?

I got upgraded to 26 the other night, and since then I am pretty much unable to edit text. The keyboard comes up and I can type, but I can’t select text, or copy or paste. I can sometimes move the text cursor by tapping within the text area, but even that is now inconsistent. Any other attempt to tap in a way that might bring up the select/copy/paste menu causes a flicker and artifacts flashing around the screen. Anyone else experiencing this?

It’s not critical problem, since I have access to an actual computer, but I often do minor edits from my phone and pretty much can’t do that now. I don’t seem to be having this problem with other sites or apps, and it’s only a problem on my phone since installing IOS26.

Pure curiosity I googled this and quite a few pages come up... perhaps have a look.

I looked at all the Google results that came up, and nothing I saw addressed this particular problem. Most of the results talk about how IOS 26 now allows you to select part of a text message and paste it into other apps, which is great (previously you could only select and copy the entire message) but not related to my problem. Some talk about disabling or adjusting the Liquid Glass related settings, or problems with the select/copy/paste menu (which I can't even access on many websites) not scrolling horizontally properly.

The problem is limited to Safari (all other apps I've tried work fine) but is not limited to Lush. A few major sites (Amazon, Google) work fine, but in MOST others (including DuckDuckGo and wikipedia), I can't select text in the editing window or bring up the copy/paste menu. In some cases, if I try to tap in the editing window after entering some text, the editing window disappears completely or becomes partly obscured by something "on top" of it in the Liquid Glass scheme. I've also tried adjusting the Accessibility and Display settings affecting Liquid Glass, as well as turning off Dark Mode, None made it better, some made it worse. Since it seems to be a safari problem, my dumb workaround for now is to use a different browser (as I am doing right now) until Apple pushes a fix.