[PATCH] "Enter" in the message box doesn't submit the form
[PATCH] "Enter" in the message box doesn't submit the form
| Issue ID: | 668 |
| Issue Category: | bug |
| Component: | ui |
| Priority: | normal |
| Status: | fixed |
| Assigned: | Unassigned |
| Version: | 0.6 |
| Milestone: | 0.7 |
"Enter" in the message box doesn't submit the form like the notice box does.
| Attachment | Size |
|---|---|
| 668_message_form_js.patch | 349 bytes |
Updates
#1
Replying to [ticket:668 evan]:
> "Enter" in the message box doesn't submit the form like the notice box does.
its working for me on current identica
Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-PT; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 ID:2008070208
#2
Didn't work for me in trunk, so I've submitted a patch. Also, shouldn't the message box have a counter like the notice box does?
#3
+1
#4
mine does. why isnt this close?
#5
Replying to [comment:4 BUGabundo]:
> mine does. why isnt this close?
BUGabundo, I'm not sure you are looking at the correct textarea message box. This ticket is in reference to the textarea at the top of the page http://identi.ca/[username]/outbox. The current JS in util.js which insures that an [Enter] keypress will submit the form does not get applied to the textarea used for sending direct messages.
Although I don't see how it's possible, even if it does work for you, this is still a bug others are experiencing, which the attached patch fixes.
#6
Replying to [comment:5 sgmurphy]:
> BUGabundo, I'm not sure you are looking at the correct textarea message box. This ticket is in reference to the textarea at the top of the page http://identi.ca/[username]/outbox.
Ahh thanks. didnt know it was about the outbox, there is no info about that!
I just tested, and it fails to work. so its a bug (or maybe a feature, if you like to write long private message)
#7
Now it‘s the other way round: Enter is sending the message at outbox but not in the notice box.
#8
Enter works in both instances. However, for direct messages there is no visual feedback that indicates the message was sent. This should be handled in another ticket.
You can also subscribe to the
RSS feed for updates to this issue.