Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Comments on Finishing link entry with enter sends the post instead

Parent

Finishing link entry with enter sends the post instead

+2
−0

I just got caught by something I consider a bug: I wanted to link to a web site, and used the link button above the entry box to do so. After I finished entering (or rather, pasting) the link into the pop-up box, I pressed enter to get it into the post.

To my great surprise, this didn't cause the link to be inserted into the post, but instead it caused the unfinished post to be posted to the site.

This is highly unintuitive behaviour which I don't believe was intended.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+2
−0

That's a bug, yes. :-( Thanks for the report.

As a workaround, if you choose[1] the "insert" button instead of using "enter", it inserts the link into the markdown and puts you back in the editor. (I don't know if we have good-enough support for keyboard-only users to choose that button. If you're such a user and we're lacking there, please let us know.)

Update: testing a fix.


  1. Already putting some new advice to work here. :-) ↩︎

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (7 comments)
General comments
celtschk‭ wrote about 4 years ago

Thanks for the reply. Actually I'm a laptop user, so I can both tap (on the touchpad) and click (on the “mouse” buttons below the touchpad). So that workaround works. A keyboard-only workaround is, of course, to just add the corresponding MarkDown manually.

Monica Cellio‭ wrote about 4 years ago

True, and what I do normally anyway (just type the Markdown links) -- for me that's faster than going through a GUI, because I'm almost always inserting the links as I compose. But if somebody is using keyboard shortcuts to navigate the GUI, and that works in general but not in this specific case, that's something I'd want to know so we could address it.

celtschk‭ wrote about 4 years ago

Actually up to now I wasn't even aware of the existence of keyboard shortcuts. I found the option to enable them in the preferences, but I can't find any description of what shortcuts are available.

Monica Cellio‭ wrote about 4 years ago

Oh whoops -- I thought we had a help topic about that, but I guess not. @celtschk see https://meta.codidact.com/questions/276697.

celtschk‭ wrote about 4 years ago

Ah, thanks. There seem to be no shortcuts related to editing, though, therefore they also cannot fail in that case. But I noticed one unrelated problem: With "go to category" (g c), only the category list seems to work (g c c), not the individual categories (like g c 1).

Monica Cellio‭ wrote about 4 years ago

Oh right; there's a separate feature request about keyboard shortcuts for editing, not yet implemented. Sorry for my confusion. Could you file a bug report on any meta about the category issue @celtschk? Thanks.