Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 371641

Summary: Orion editor throws up the virtual keyboard on iOS when scrolling
Product: [ECD] Orion Reporter: Chris McGee <cbmcgee>
Component: ClientAssignee: Silenio Quarti <Silenio_Quarti>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: christophe.cornu+eclipse, Silenio_Quarti
Version: unspecified   
Target Milestone: 0.5 M1   
Hardware: Other   
OS: iOS   
Whiteboard:

Description Chris McGee CLA 2012-02-15 11:19:12 EST
In Rational Team Concert the Orion editor is currently hosted as a read-only view. I could see this being an annoyance even if it was read-write when you try to hide the keyboard and simply scroll by dragging your finger.

Open up the Orion editor using an iPad
Touch somewhere in the editor pane
Touch the "Hide Keyboard" button on the bottom right of the iPad's virtual keboard
Try scrolling by dragging your finger up/down along the editor pane
Comment 1 Christophe Cornu CLA 2012-02-15 11:28:16 EST
Chris, which iPad, safari and iOS versions are you using?

On the RTC side, we're using an older version of the orion editor 0.2M2 - we use  it in read only mode. Safari/iPad isn't a committed platform yet but we've been asked to take steps in that direction. If there's a small fix, we can patch our own version until we move to a newer version.
Comment 2 Chris McGee CLA 2012-02-15 14:07:19 EST
Too bad eclipse bugzilla doesn't have iOS categories for platform.

I tried this on an iPad 2 with iOS version 5.0.1.
Comment 3 Silenio Quarti CLA 2012-03-12 15:20:12 EDT
This is not an issue any more with the latest code (after bug#371646).  The keyboard does not pop up as you are scrolling. It will only pop up when you tap the editor.

Christophe, I am not sure there is a easy hack on top of 0.2 M2 I can offer. The only thing I can think would also disable the copy menu. Which is not a big deal, given that is broken (see bug#371266). Do you want try it out?

There are so many things broken before bug#371646. I believe you are better off moving to the latest version.
Comment 4 Christophe Cornu CLA 2012-03-12 15:59:43 EDT
Thanks Silenio, it's great to know it's fixed in the latest.