Bug #489
closedTable view cell not clickable within a dialog
0%
Description
The cells in the table view appear not clickable (or incorrectly clicked and then opened the editor of a different cell) when the table view is placed inside a dialog, and the background vertical scroll bar offset is not zero.
Here are the steps to reproduce the bug:
- Create a page with many elements, so that a vertical scrollbar appears.
- Create a WTableView inside a WDialog.
- Resize WTableView to a certain size and set
progressive-bootstrap
tofalse
, so that a vertical scroll bar appears for rendering a large table. - Populate WTableView with many rows.
- Make all cells editable.
- Bring up the dialog and verify that the cells are clickable.
- There are two scroll bars: one in the dialog and one in the background window. Move the scroll bar in the background window to a different position other than the top position.
- Click any cells inside the table view.
- Observe that the cell is either not clickable or is clicked into a wrong cell.
Files
Updated by Thian-Peng Ter over 13 years ago
Minor update to step 3. I just found out that it is unnecessary to set progressive-bootstrap
to false
to turn on the vertical scroll bar. For some reason, depending on how or when the table view is created, Wt may show the navigation bar instead of a vertical scroll bar.
Updated by Koen Deforche over 13 years ago
Hey Thian-Peng,
This seems like a bug in the positioning calculations.
We've changed something related to this in the last version of Wt. What version are you using (Wt 3.1.3, 3.1.4 or latest git) ?
Regards,
koen
Updated by Thian-Peng Ter over 13 years ago
- File bug489-example.zip bug489-example.zip added
I used the latest git. I finally found some time to create an example to illustrate the issue. Please refer to the attached file.
Here are the steps to reproduce the bug using the example:
- Run DialogExample and observe the page shows with a vertical scrollbar.
- Scroll to the bottom of the page and then click the "One liner" button to bring up a dialog.
- Single-click on any cell in the table and observe that clicking on the cells would not open an editor.
- In the background window, scroll to the top.
- Go back to the table in the dialog, click on any cell and observe that an editor is now opened.
Updated by Koen Deforche over 13 years ago
- Status changed from New to InProgress
- Assignee set to Koen Deforche
Updated by Koen Deforche over 13 years ago
- Status changed from InProgress to Resolved
Updated by Thian-Peng Ter over 13 years ago
Thank you for looking into this. I tried running the example again using the latest git (revision 5835dce9). Unfortunately, the issue was not resolved. Depending on the size of the window, each cell is either not clickable, or the editor of a different cell is incorrectly opened.
Would you please kindly look into it again? Thank you.
Updated by Koen Deforche over 13 years ago
Hey,
I think I forgot to minify the Wt.js to Wt.min.js before pushing the changes to public git.
You can help yourself out by simply copying Wt.js to Wt.min.js before building Wt, I currently have no access to our VPN to correct this (I am currently traveling).
Regards,
koen
Updated by Thian-Peng Ter over 13 years ago
Yes, this does fix the problem. Many thanks!