shiftedit
shiftedit copied to clipboard
Clicking File List button does not open panel, and sliding pointer into list closes the panel.
The enclosed video shows the following:
- The Shift-Edit tab is refreshed (as shown by the green status prompt flashing at the top of the window).
- The File List button is clicked (as shown by the button glyph displaying a round border) but the panel does not open.
- The panel is dragged open with the pointer but the two times the pointer is slid back into the file list, the panel closes.
Not shown: If the pointer is moved up and over to the left, it can be slid down into the file list without it closing.
Device: ChromeOS (version 99.0.4844.94) on Chromebox i5 processor w/ 16GB RAM.
https://user-images.githubusercontent.com/19599626/160762593-3127c581-0217-465f-ad54-8033838c6ec4.mp4
Tested on windows with the same version and was not able to recreate this. I pushed an update to fix the inconsistent button border. You could try manually resizing the file pane on first load instead of clicking the button.
Thank you for checking. Of course most of us who use your product understand the challenges of operating on multiple platforms.
For me, the primary difficulty arises while using a touch-screen tablet to quickly check on a problem. The browser's swipe-back feature prevents me from manually opening the file panel, and so I am unable to use Shift-Edit unless the necessary files are already displayed in tabs. I believe adding "overscroll-behavior-x: none;" to your CSS might address that problem.
On Thu, Mar 31, 2022 at 9:09 AM Adam Jimenez @.***> wrote:
Tested on windows with the same version and was not able to recreate this. I pushed an update to fix the inconsistent button border. You could try manually resizing the file pane on first load instead of clicking the button.
— Reply to this email directly, view it on GitHub https://github.com/adamjimenez/shiftedit/issues/386#issuecomment-1084794817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEVRCCXBENDJL5FPTM2RS53VCXE4FANCNFSM5SAZ3BKQ . You are receiving this because you authored the thread.Message ID: @.***>