Cthulhu wrote:
I have *never* felt this forum was dismissive or was a bug reporting mechanism, and I'm sorry you've encountered that.
It's not that I've encountered it. It's more that I'm guilty of it. 😄
I don't have a way to test something that's not on our network, but watching Wireshark there is too much HTTPS traffic even just sitting idle for me to really figure this one out.
Two things. First of all, you should know that any text field will radically change its behaviour when you click inside it. A text field may have any number of operations like drag and drop, etc. But when you click in it, the old text literally gets replaced with a new text view object. While active, the new field has totally different behaviour, different active menu items, etc.
Maybe you should look more closely at your network. Most of the Sequoia problems that people are reported are related to the network - rotating WiFi addresses, firewall, and VPNs. The Safari text field is pretty special. It does an awful lot of networking behind the scenes. It will even start loading a website before you finish typing in it.
My guess is that is what is happening in your case. Your networking isn't working correctly and that field is still doing work, or waiting for a response. It isn't transitioning into a read-for-user-interaction state the way it should. When you drag it, it has to create a draggable internal object that can be saved in favourites or on the desktop as a webloc file. But since the internal networking hasn't finished yet, it hasn't built that draggable object yet. Therefore, you can't drag it.
