Bug 565876 - Touch-Scrolling not working correctly (iOS) AND position: fixed and the virtual keyboard
Summary: Touch-Scrolling not working correctly (iOS) AND position: fixed and the virtu...
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 3.9   Edit
Hardware: Other iOS
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 577625 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-08-07 03:42 EDT by Engin Bilen CLA
Modified: 2022-02-10 05:31 EST (History)
2 users (show)

See Also:

Attachments
Scrolling issue and virtual keyboard fixed element issue (11.25 MB, video/mp4)
2020-08-07 03:42 EDT, Engin Bilen CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Engin Bilen CLA 2020-08-07 03:42:26 EDT 
Created attachment 283810 [details]
Scrolling issue and virtual keyboard fixed element issue

My Eclipse e4 application contains ScrolledComposite, ComboViewer, Table etc. 


---Scrolling issue--- 
A scrollable Table (or Tree), ComboViewer or ScrolledComposite placed withina ScroleldComposite can not be scrolled by touching the Table-Items, only using the scrollbar.

The first problem occurs only on IOS Firefox and Safari not on Chrome and not on Android(Firefox, Chrome).


---CSS Issue---
When I push the screen to the right and left with its touch feature, there are momentary shifts on the screen.

The second problem occurs only on IOS Firefox and Safari not on Chrome and not on Android(Firefox, Chrome).


---Virtual keyboard issue on mobile browser---
When I focus on the screen and the keyboard becomes visible, the fixed item starts to scroll with the page. Is it bug or something? And is there any solution for this?


I recorded all the problems with a video. I think the video can be helpful.

Many thanks
Engin Bilen
Comment 1 Ivan Furnadjiev CLA 2022-02-10 05:31:30 EST 
*** Bug 577625 has been marked as a duplicate of this bug. ***