hitting PgUp when composing a post obscures the page & requires restart

[cameralibre]

Patchbay-7.15.0-linux-x86_64.AppImage
Ubuntu 18.04 (Budgie Desktop)

Using PgUp & PgDn normally has the expected effect within patchbay, and still work as expected when the 'compose/reply' input is focused. However, once there is some content in the input, hitting PgUp will cut the visible space in half, make my tabs inaccessible, and make it impossible to scroll up and read the thread I was replying to (which is usually my reason for hitting PgUp in the first place). When this happens I have to copy the text I was writing, restart patchbay, navigate back to the thread and re-enter it.

(I've used halfscreen tiling for these screenshots but the effect is the same whether halfscreen or fullscreen)

[christianbundy]

Reproduced!

I'm unclear on whether this is a Patchbay thing or an issue with Hypertabs, but unfortunately I'm having trouble getting the Hypertabs example going.

cc: @dominictarr @arj03 @mixmix

[christianbundy]

Btw, I know this isn't a great workaround but you can fix this with Ctrl+R which is slightly faster than restarting Scuttlebot + Electron. Definitely still copy your text first though!

[mixmix]

This one drives me wild. I thought is accidentally fixed out butt it's back. One poor solution wild be to listen for pageup down keystrokes and suppress them if context is the composer. Other than that i guess it's searching gee dom for some weak css

…

On Sat, 20 Oct 2018, 09:58 Christian Bundy, ***@***.***> wrote: Btw, I know this isn't a *great* workaround but you can fix this with Ctrl+R which is slightly faster than restarting Scuttlebot + Electron. Definitely still copy your text first though! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACitngEfxARQV3HlxQ_iGvRF9-3FGqPXks5umjzYgaJpZM4XxXhs> .

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Powersource]

This is funny, patchwork has the exact same bug (see link above).

[mixmix]

Oh I fixed this (I hope!) like 327aa3e or 2c4c4e3

@cameralibre / @Powersource / @christianbundy care to test and confirm? I think if one of you can't reproduce, then please close this

[cameralibre]

I can't reproduce it - looks like you squashed this one.

🐞️🤺️
nice one @mixmix !

[mixmix]

thanks sam! welcome back btw

…

On Jun 3 2019, at 2:05 pm, Sam Muirhead ***@***.***> wrote: Closed #268 (#268). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (#268?email_source=notifications&email_token=AAUK3HV6L2G4FDREOIB5WJLPYR4AHA5CNFSM4F6FPBWKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORYJAZGI#event-2383547545), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAUK3HW2QSEUA2EEXJIMK3TPYR4AHANCNFSM4F6FPBWA).