Ctrl+[some letters] submits posts
-
Sorry for the little mess ITT, was too lazy to make a second one for the testing.
Both Ctrl+J and Ctrl + M (and probably a few more letters, which I haven't tested) seem to submit posts on Vivaldi, which is unexpected and can cause half-written posts to be submitted.
I tried Ctrl+J and Ctrl+M on Edge and it doesn't, but that's probably because Edge intercepts those combinations for its own uses.
-
This post is deleted!
-
This post is deleted!
-
testing in chrome
In Chrome, ctrl + j brings up the Downloads tab
-
sdf
Ctrl + M does do it in Chrome.
-
This is a test for Chrome on Mac:
Edit: CTRL + J submits
Edit 2: CTRL + M submits as well.
-
Firefox for Linux doesn't submit. Ctrl+J does nothing (that I can see) and Ctrl+M is mute tab. Tested some others too and the only triggers for NodeBB that I found working was inserting italicized and bolded text into the editor.
-
Carriage Return and Line Feed, our good friends.
FWIW, Ctrl-M in Vivaldi for Windows submits and does its normal action of toggling the menu bar.
-
ctrl+m
-
Hmm...here's a couple choice bugs where Chromium has been misdirecting Ctrl-M. Something could have regressed a bit further than they (or the people making other browsers, Vivaldi being a Chromium browser) last thought.
-
Carriage Return [Ctrl-M] and Line Feed [Ctrl-J] are both "new line" type characters.
-
@parody said in Ctrl+[some letters] submits posts:
Hmm...here's a couple choice bugs where Chromium has been misdirecting Ctrl-M. Something could have regressed a bit further than they (or the people making other browsers, Vivaldi being a Chromium browser) last thought.
Vivaldi also had a fair share of its own "passing captured key combos to the browser anyway" bugs when I used it, there might be some of that lingering around still. You'd think they'd fix them all in one go but no, I know they fixed the "backspace in a
contenteditable
field navigates back" thing, but things likeCtrl
+S
would still pass the command to the browser even if you captured it in the page.
-
@parody Oh dear, so it's most likely a chromium bug then.
Apparently related to ASCII control codes. Someone probably forgot to tell one of their "senior" developers that people don't generally access computers with teletypewriters anymore.
-
@anonymous234 said in Ctrl+[some letters] submits posts:
Someone probably forgot to tell one of their "senior" developers that people don't generally access computers with teletypewriters anymore.
Maybe it's a new hipster thing like using vi
-
@anonymous234 said in Ctrl+[some letters] submits posts:
@parody Oh dear, so it's most likely a chromium bug then.
Apparently related to ASCII control codes. Someone probably forgot to tell one of their "senior" developers that people don't generally access computers with teletypewriters anymore.
But I have heard an "upgrade" is coming soon...