A user, TallTed, reports that in Discourse 3.2.0.beta1-dev, the keyboard shortcuts Option+Up and Option+Down no longer function in the post editor — these previously moved the cursor to the top or bottom of the current or adjacent paragraph, significantly aiding editorial workflow. Other shortcuts (Option+Left/Right, Command+Up/Down, etc.) still work. The issue appears tied to a recent upgrade and is reproducible on both meta.discourse.org and another Discourse site, using Chrome on macOS Mojave. TallTed confirms the shortcuts worked historically across all Mac text editors and suspects a recent Discourse change. Canapin acknowledges the behavior as unusual for Discourse and agrees it may be a regression. sam confirms the team investigated but couldn’t identify the cause, and has tagged the issue pr-welcome to invite community contributions. TallTed humorously notes his height (6’8”) and reiterates the shortcuts’ long-standing utility across platforms.
Option-left and option-right still work — these move the cursor one word to the left or right, respectively.
Command-left and command-right still work — these move the cursor to the left or right side of the edit window, respectively.
Command-up and command-down still work — these move the cursor to the top or bottom of the post, respectively.
Option-up and option-down no longer work — these used to move the cursor to the top or bottom of the current paragraph, or to the top or bottom of the next paragraph if starting from the top or bottom of the current paragraph.
Suddenly, in 3.2.0.beta1-dev (f32c95c1b9), option-up and option-down do nothing, drastically impacting my editorial productivity.
I cannot edit my post? That’s odd, and frustrating!
FWIW, I’m running Google Chrome Version 116.0.5845.110 (Official Build) (x86_64) on macOS Mojave 10.14.6 (18G9323), and seeing this behavior on this site as well as the one I was originally working on.
I do have a number of browser extensions installed, but this behavior isn’t seen in text entry boxes on any other sites, so I’m comfortable blaming it on Discourse.
It would be great to at least get an ack, even if nobody thinks this is worth fixing quickly if at all.
I’m a mac beginner, I’ve never used ⌥+↑ or ⌥+↓ before.
But I notice it works as you describe on various text editors but not in Discourse’s composer. If you’re certain it worked before, then I think it may be considered as a bug recently introduced.
If you’re certain it worked before, then I think it may be considered as a bug recently introduced.
Yes, quite certain. I’ve been using Macs since the original, and these key chords were significant productivity boosters way back when (I don’t remember exactly when they first arrived, nor in what software), and I’ve used them everywhere ever since. I can’t think of another tool where they don’t work, today.
