Since the Pro 3.x update, inline editing, especially the double-click to enter inline editing has been quite problematic. These sentiments are echo’d by my entire team to remove any possibility that my PC setup changed at the same time Pro 3.x was released.
Other issues with this include little to no tolerance for tiny mouse movements. If one double clicks and the mouse moves even a couple of pixels during the double click sequence, as is common, inline editing won’t start. It’s treated as two single clicks.
Lastly, sometimes the mouse click interceptor gets very confused and will enter inline edit mode, immediately exit it (element remains selected), and then flash the page. OR it will highlight the line or paragraph. This means the click interceptor has failed to take proper control and the OS or browser is preempting your interceptor.
In a nutshell, this 3.x release has been a giant regression for devs who work quickly and efficiently. Our team moves at the speed of light - we use every keyboard shortcut, time-saving practice, etc. Pro 3.x as it is right this moment is not compatible with fast development. There are too many stop points, broken functions, etc. 2.x was superior in every possible way in this aspect. So much so that we’d gladly revert back to 2.x if it were possible.
Please do better on this. I realize many of your users, beta team, and dev team work slower than us and may never encounter these issues. But they certainly persist and after 2 weeks of dealing with them, gathering feedback, and testing the scenarios, we have to speak up about it.
We all use Chrome (latest) on Win 7.