Search Issue Tracker
Won't Fix
Votes
2
Found in
5.6.3p2
Issue ID
953479
Regression
No
[UWP] Pasting a text into an InputField does not work with UWP touch screen keyboard
Steps to reproduce:
1. Open the attached project
2. Switch platform to Universal Windows Platform
3. Build to generate Visual Studio project
4. Open Visual Studio solution
5. Build and Run the app (doesn't have to be a Touch device)
6. Copy text using the buttons or from any other app
7. Select the input field to give it focus (opens screen keyboard if on a touch device)
8. Try to paste text using keyboard shortcut (Ctrl+V) from either physical or screen keyboard
9. No text is pasted. Pasting in an other app works fine
NOTE: It is possible to test using Touch without an actual device. Visual Studio includes a touch "Simulator" device, to which you can deploy the app and inject Touch events (it's similar to a Windows Phone emulator). You might need to manually install it from Visual Studio Installer.
Actual results: No text is pasted. Pasting in an other app works fine
Expected results: Copied text is pasted
Reproduced with: 5.5.5p1, 5.6.4p2, 20171.2p3, 2017.2.0p2, 2017.3.0b9, 2018.1.0a4
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
tsomerville
Mar 20, 2018 04:32
Meant to also say, my debugger gave me an WPF Datagrid OpenClipboard Failed error. It blows up in the stacktrace way down in Kernel.dll or something around there. if that clue means anything to you.
tsomerville
Mar 20, 2018 04:30
I am using 2017.2.0.f3 and have the same problem. If I disable the touchscreen device (windows key -> device manager -> Human Input Device Touchscreen (right click and disable), and restart my app, I don't have the problem.
Considering using TouchscreenKeyboard.isSupported or something to avoid this, but very frustrated to find out about this!