| Summary: | Cell editors overlap Table header when scrolling (mouse wheel) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | r k <rkunitzky> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | ivan, sgouta2, tbuschto | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 2.0 M1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | sr152 | ||||||
| Attachments: |
|
||||||
|
Description
r k
Reproducible with Controls Demo - TableViewer tab: 1. Add 100 items 2. Enable cell editors 3. Activate a cell editor and use mouse wheel to scroll down - cell editor is visible (or partly) on the Table header Set the priority to P1 as this is a regression. I have developed a workaround. I use a scrollbarlistener and the table topIndex together with a list of controls created during the table generation. Whenever the table is scrolled, it detects the topIndex and the lastTopIndex and calculates the amount of objects to hide or to show. The only input needed is the amount of controls p. row. It works fine for me. Fixed with commit c605c79f34312b0471e7e2cf881fa478865ccc66 by setting ZIndex of GridHeader. Created attachment 222682 [details]
Image overlaps column header
Seems like we are getting the same problem again with RAP 1.5.1. Can we reopen this issue in that case? Will you manage to look at it without code snippet? (In reply to comment #3) > Fixed with commit c605c79f34312b0471e7e2cf881fa478865ccc66 by setting ZIndex > of GridHeader. Hello I recreated this defect with RAP 1.5.1 but noticed that it is fixed in version 2.0.0. We are currently using version 1.5.1, can I refer to this defect or should I create a new defect? Regards, Seif (In reply to comment #6) > (In reply to comment #3) > > Fixed with commit c605c79f34312b0471e7e2cf881fa478865ccc66 by setting ZIndex > > of GridHeader. > > Hello > I recreated this defect with RAP 1.5.1 but noticed that it is fixed in > version 2.0.0. > We are currently using version 1.5.1, can I refer to this defect or should I > create a new defect? > Regards, > Seif I will reopen this bug and we will consider to fix it for 1.5.2. Keep status fixed, but mark it for consideration for 1.5.2 I'm fine with backporting the patch to 1.5.2, but for the master branch, I'd prefer to have a pointer to the bug, preferably in a comment with the test. Otherwise it won't be clear why the z-index is set to 2000. Backported to 1.5-maintenance branch with commit 12e785443228094bc26748cc117d35ef2ba82c7b. |