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 »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

77%
+5 −0
Q&A button automatically enables when using tab and enter

I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed tab twice ...

0 answers  ·  posted 3y ago by deleted user  ·  edited 3y ago by deleted user

Question bug comments
#3: Post edited by (deleted user) · 2021-10-21T07:06:12Z (about 3 years ago)
the button was wrong
  • button automatically enables when using shift and enter
  • button automatically enables when using tab and enter
  • I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed `shift` twice then, clicked on `Enter`. Then, I just got an error 422 unprocessable.
  • Usually, we were disabling submit button. But, when using shift and enter that button enables automatically. I am not sure if it happens in other Browsers. I am using Chrome.
  • I think Ruby can do something for the reason (My browser is destroying JS :D).
  • (The same thing happens with Firefox also (tested))
  • I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed `tab` twice then, clicked on `Enter`. Then, I just got an error 422 unprocessable.
  • Usually, we were disabling submit button. But, when using tab and enter that button enables automatically. I am not sure if it happens in other Browsers. I am using Chrome.
  • I think Ruby can do something for the reason (My browser is destroying JS :D).
  • (The same thing happens with Firefox also (tested))
#2: Post edited by (deleted user) · 2021-08-20T07:51:10Z (about 3 years ago)
  • I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed `shift` twice then, clicked on `Enter`. Then, I just got an error 422 unprocessable.
  • Usually, we were disabling submit button. But, when using shift and enter that button enables automatically. I am not sure if it happens in other Browsers. I am using Chrome.
  • I think Ruby can do something for the reason (My browser is destroying JS :D).
  • I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed `shift` twice then, clicked on `Enter`. Then, I just got an error 422 unprocessable.
  • Usually, we were disabling submit button. But, when using shift and enter that button enables automatically. I am not sure if it happens in other Browsers. I am using Chrome.
  • I think Ruby can do something for the reason (My browser is destroying JS :D).
  • (The same thing happens with Firefox also (tested))
#1: Initial revision by (deleted user) · 2021-08-20T03:40:59Z (about 3 years ago)
button automatically enables when using shift and enter
I never thought of it. Recently, I was going to write a comment (Starting a new thread) with 14 characters. I didn't look at character lengths. After completing my comment I just pressed `shift` twice then, clicked on `Enter`. Then, I just got an error 422 unprocessable. 

Usually, we were disabling submit button. But, when using shift and enter that button enables automatically. I am not sure if it happens in other Browsers. I am using Chrome.

I think Ruby can do something for the reason (My browser is destroying JS :D).