Keyboard now automatically calls on tapping-&-holding on a text in an input box, instead of only on tapping-&-releasing on an input box (iOS/iPadOS 27)…

Thanks for that additional explanation. Step 4 (pinch to zoom) appears to have been an important detail. Doing that first, followed by using iOS's traditional multitouch gestures causes text field elements to misbehave badly.

If you don't "pinch to zoom" everything works as it always has.

Given your suspicion it's a recent change perhaps it's a manifestation of Liquid Glass. Who knows.

File Feedback as I suggested earlier, but in so doing endeavor to keep things simple. Definitely provide step by step instructions as you wrote, but take a very fundamental approach. Use the most basic text fields as an example, and ideally limit your illustrations exclusively to Apple products and Apple services — things under their sole control. HTML input fields offer a wide variety of options, which are further complicated by Javascript and other code, but from my admittedly brief interaction with the website you mentioned and this site (Apple Community) attention from Apple seems justified.

You will increase the likelihood of getting their attention by keeping things absurdly simple. Step 1, do this, Step 2, do that, etc.

Conversely, if you provide examples using non-Apple products and services or if your product (Mac, iPhone, iPad etc) is affected by non-Apple products (extensions, add-ons etc) they will take a "not our problem" view of your concern.

Apple surely receives thousands of Feedback submissions every day, and it would be unreasonable to expect they don't use some kind of automated review of them before a human gets involved. Even then they won't respond to you directly (they might) but if you keep the suggestions above in mind your Feedback is almost certain to to get their attention... eventually.

To adopt a military term, file and forget. Then wait.

They removed my reply to you ‘cause exactly, how is a link that I’m providing to you an inappropriate link???

That's not for us to decide. By way of explanation though, at one point in the past this site became threatened with an increase in the frequency of thinly disguised or overt attempts at leveraging it for free advertising, personal gain, or (worse yet) nefarious purposes that can best be characterized as vandalism. The most successful company on Earth became an appealing target for that sort of malice. It was bad. Apple reacted. The exponential rise of "AI" has only accelerated those threats. So, here we are.

Using links to Apple products and services is certainly ok, as are links to many popular and mundane websites. Anything else might just get summarily rejected, along with a nastygram in your inbox.

No, but it doesn't matter. You identified repeatable behavior that can only be described as an annoyance, at best. None of us can fix that. Feedback is the way to go. Just keep your duplication instructions devastatingly simple, and inescapably limited to something that Apple can fix on their own. In other words don't leave them any "you're holding it wrong" excuse.

I can't duplicate that behavior, but I am not certain I completely understand your concern. Tapping and holding text in the website you referenced in the screenshot you provided does exactly nothing, other than position the cursor in the general vicinity of the tapped area (which you can drag). Double-tapping text will highlight (select) space-delimited text and summon a familiar contextual menu with its cut / copy / paste options for that selection. If the selected text happens to be a phone number (for example) the contextual menu will add call / video / message to that contextual menu consistent with Apple's data detection algorithms. As that document explains, some of that behavior is determined by the content developer so you can expect it will behave differently among different websites with text entry fields.

Triple-tapping text expands the text selection to paragraphs (line break delimited).

Those options (tap, double- or triple-tap, tap and hold) are all we can do with text. None of this is new, so I am at a loss to understand what's going on with your iPhone with the services you're using.

I can find no explanation for Apple's (likely automated) response alleging discussions of beta software, so I understand your frustration with that. Apple's "AI" may have simply erred, or perhaps it edited some offending content no longer available to us. Since your original post was edited and some content presumably removed, the participants of this site simply have no way to know what happened. Perhaps it was a mistake. Don't take it personally.

In any event if you have reason to believe something is amiss with the way Safari is behaving, or if you simply disagree with the way it works, the right place to make your concerns known is to file Feedback, here: Product Feedback - Apple. It's the only way Apple will hear about it. This site is not the right place, for a number of reasons, not the least of which is that Apple doesn't use it for that purpose.

Apple just did what on me!? 😦

I’m trying to explain the whole situation, & show just a little bit of evidence of where I’d notice the problem more at, & they just edited & removed it from my discussion post here, basically as now nobody is gonna know what I’m talking about, where I’m trying to show of where I’d notice the problem more at, & plus as they just edited & removed the last sentence in my last paragraph, basically now making it look like if I got interrupted or if I forgot what I wanted to say at the end or so.

I don’t believe this, that Apple would try to mess this all up on me & try to cause confusion for any people, who might reply to this discussion post here of what I’m trying to talk about with the annoying situation that I’m having on iOS/iPadOS 27. 😑

🤦🏻‍♂️

Here we go again with Apple… 😑

They removed my reply to you ‘cause exactly, how is a link that I’m providing to you an inappropriate link???

Well, anyway, here’s what I’m trying to say & explain to you in my reply. ⬆️

Even though that may be hard to understand what you just said there in your response, let me ask you another question:

Do you have Discord at all?

I’m thinking that maybe we can talk more about this on there, & where I can like send you a screen recording for you to get more of the idea on what I’m talking about with the keyboard calling problem that started occurring with iOS/iPadOS 27.

Um…okay.

Basically in your other words, you want me to try & reach out to Apple again via feedback about the keyboard calling problem, & which hopefully will they eventually then see it & try to fix it with an iOS/iPadOS Software Update?

Also, just in your opinion, don’t you think that this is a bug with the keyboard calling situation that currently not many people are experiencing, but at least me?

To me, I’m hoping that it’s just a bug that can hopefully be fixed soon by Apple, but I just want to hear from you as well, to get your opinion on this keyboard calling situation.

Let me just ask you a question first:

Are you on iOS/iPadOS 27?

Yes.

iPhone though, not sure about the iPad. I'll confirm the iPad when I get around to it, but I'd be surprised if it works any differently.

If it concerns you, file Feedback. It doesn't concern me. If it did I would file Feedback.