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 »
Users Search
Help Dashboard Sign In Sign Up
Q&A Blog
Q&A
Posts Tags Edits
Ask Question

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.

Comments on Button is disabled without any explanation when title is too short

Parent

Button is disabled without any explanation when title is too short

+5
−0

When I was writing the post. My title was too short for post that. But, I was thinking why button is disabled. Since, I had worked on disabling button that's why I knew my post's title was too short to post that. Hence, I added some more context to title. But, it could be completely confusing for a new user or, who haven't had idea of that.

User-friendly UI suggestion required hence, discussion tag.
feature-request discussion editor user-interface
posted over 3 years ago
3y ago by Moshi‭
deleted user
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?

2 comment threads

User-friendly UI (1 comment)
further confusion (1 comment)
Post
+0
−0

Bringing it as answer to know if it's better.

We are currently showing red border when the length of post body is less than 15 or greater than 30000. The same effect was done on comment also.

There's a problem in Chrome based browser (Chrome and Chromium) (I can see the same issue with Microsoft edge also). Chrome usually shows an effect when you focus on the textarea. That's not a QPixel issue cause it works fine in Tor browser and Firefox (I haven't test it anywhere else).

For textarea :

For textarea : while focusing the field

image whlie not focusing without focusing image

Same effect for title

image without focus

posted about 3 years ago
CC0
3y ago
deleted user
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

So you say that Chrome/Chromium is not supported on this site? Because otherwise it not working there... (6 comments)
I see the border in Chrome (1 comment)
So you say that Chrome/Chromium is not supported on this site? Because otherwise it not working there...
celtschk‭ wrote about 3 years ago
copy link

So you say that Chrome/Chromium is not supported on this site? Because otherwise it not working there is an issue of QPixel.

deleted user wrote about 3 years ago
copy link

There's no issue of QPixel it's just browser effect. I have edited the answer it might be helpful. Sorry for confusion

celtschk‭ wrote about 3 years ago
copy link

If a browser effect of a supported browser means it doesn't work as expected, it is an issue of QPixel. Even a blatant browser bug that's not worked around would be.

Trilarion‭ wrote almost 3 years ago
copy link

Should Chrome display that border but doesn't? If yes, it's a bug in Chrome, but still a problem for QPixel. In that case, maybe a different additional thing can be done for Chrome users. Chrome is widely used and probably should be supported, even with bugs in it.

deleted user wrote almost 3 years ago
copy link

Trilarion‭ according to celtschk, if a expected UI didn't work as expected in browser X but worked properly in browser Y than it's a coding issue rather than browser's. But for now, I have never seen similar thing earlier that's why I don't have any idea how to solve it. And I am not interested for further research cause I don't code too much now. I code once in a month.

Trilarion‭ wrote almost 3 years ago
copy link

I think it's good that you reported the problem (with Chrome or the code or both) because whoever it is to blame it either needs a fix, a workaround (could even be an additional hint) or a rejection. The important question is what we could do about it. Maybe the programmers have an idea there. I just wanted to say that I think Chrome is widely used enough that it should be supported.