Forgot to add: The last straw was when I opened Opera, and found all but 1 of my extensions were gone..... vanished. I went to one of my other computers that was set to sync the same things, hoping it still had all the extensions on it. They were gone from that system also. I wasnt about to go through the process of downloading all my extensions again, and get them all set up. Like I said, tired of fixing Opera every time an update breaks something. Went back to Firefox instead, and have had no issues.
We have been asking for years to return Opera to its original form. But I don't think the developers are at all in the mood for that.
I just don't understand why they take this initiative that is so detrimental to the smooth operation of Opera in all Operating Systems.
For this new form of border is horrible, and impractical; either on Linux or Windows.
In some versions of Opera/Chrome it has worked as expected. My version of Synergy has never changed. This effects no other software. I realize that's not definitive, but all the available evidence seems to point to WebKit.
Thanks for the bug report (even if it's for chromium and not Chrome).
Thanks for that, kgiii.
(You won't or at least shouldn't need sudo in your own home directory.)
No problem. Glad to have helped and no, you shouldn't need elevated permissions but I figured I'd mention it. I've been on a least privilege kick for a little while (I hang out on the AskUbuntu site a bit as well as StackExchange/Overflow and Unix) and it's kind of become a habit. I see people who will suggest stuff like sudo nano ~/bash_history and quietly edit it out. This stuff is meant to last forever, I guess.
Anyhow, I should write some sort of extension for this. It'd be nice if Opera opened up access to their sync servers. I'd then write an extension to sync the darned dictionary.
I use leafpad ~/.config/opera/"Custom Dictionary.txt" to edit. Quotes are required due to the space in the file name. Or... leafpad ~/.config/opera-beta/"Custom Dictionary.txt"
I suppose you probably already know all of this but someone might come along afterwards and not know. sighs It's that writing for AU that's made me do it! Who knows? The next person to come along might want to know. Hmm... You could probably alias it, if you used it often enough to warrant adding it to the list.
If you agree it should be done but for different reasons, wouldn't it make more sense to say "yes, do it for these reasons also" rather than argue that my reasons are insufficient?
Directly to your point though, the developers may be a long way off from fixing all the features of both the dialog and any that remain in the tree. Separating these functions would allow any user, developer, or tester to enable one or the other as their use-case demanded.