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

71%
+3 −0
Q&A Input box is not on screen after pressing "Start new comment thread" with expanded comments

If comment threads below a post are already expanded, then the input box that appears after pressing the "Start new comment thread" button is too far down the page to be visible. This makes it look...

0 answers  ·  posted 1y ago by trichoplax‭  ·  edited 1y ago by Monica Cellio‭

#3: Post edited by user avatar Monica Cellio‭ · 2023-12-04T04:20:10Z (about 1 year ago)
#2: Post edited by user avatar trichoplax‭ · 2023-06-16T07:59:05Z (over 1 year ago)
Add a comma
  • If comment threads below a post are already expanded, then the input box that appears after pressing the "Start new comment thread" button is too far down the page to be visible. This makes it look like the button is broken, unless the user thinks to scroll down the page and look for the input box.
  • In the following screenshot, 2 expanded comment threads is more than enough to move the new input box out of the visible area, requiring scrolling down to find it. In some cases a single expanded comment thread would be enough.
  • Everything except the button and the resulting input box have been blurred out, to make clear how far apart they are:
  • ![A tall blurred out comment thread separating the "Start new comment thread" button from the resulting input box](https://meta.codidact.com/uploads/zadu0pmujppjj4j8c2hc0gnzalnw)
  • Could pressing the "Start new comment thread" button be made to automatically scroll the page to the input box that appears?
  • Alternatively the buttons could be placed below the existing comment threads rather than above them, then no scrolling would be required as the input box would always appear immediately below the button.
  • Another alternative would be to make the input box appear above the existing comment threads rather than below them, so it is always immediately below the button.
  • My preference would be either of the approaches that do not require automatic scrolling, as this has less opportunity to confuse the user.
  • If comment threads below a post are already expanded, then the input box that appears after pressing the "Start new comment thread" button is too far down the page to be visible. This makes it look like the button is broken, unless the user thinks to scroll down the page and look for the input box.
  • In the following screenshot, 2 expanded comment threads is more than enough to move the new input box out of the visible area, requiring scrolling down to find it. In some cases a single expanded comment thread would be enough.
  • Everything except the button and the resulting input box have been blurred out, to make clear how far apart they are:
  • ![A tall blurred out comment thread separating the "Start new comment thread" button from the resulting input box](https://meta.codidact.com/uploads/zadu0pmujppjj4j8c2hc0gnzalnw)
  • Could pressing the "Start new comment thread" button be made to automatically scroll the page to the input box that appears?
  • Alternatively, the buttons could be placed below the existing comment threads rather than above them, then no scrolling would be required as the input box would always appear immediately below the button.
  • Another alternative would be to make the input box appear above the existing comment threads rather than below them, so it is always immediately below the button.
  • My preference would be either of the approaches that do not require automatic scrolling, as this has less opportunity to confuse the user.
#1: Initial revision by user avatar trichoplax‭ · 2023-06-16T07:57:20Z (over 1 year ago)
Input box is not on screen after pressing "Start new comment thread" with expanded comments
If comment threads below a post are already expanded, then the input box that appears after pressing the "Start new comment thread" button is too far down the page to be visible. This makes it look like the button is broken, unless the user thinks to scroll down the page and look for the input box.

In the following screenshot, 2 expanded comment threads is more than enough to move the new input box out of the visible area, requiring scrolling down to find it. In some cases a single expanded comment thread would be enough.

Everything except the button and the resulting input box have been blurred out, to make clear how far apart they are:

![A tall blurred out comment thread separating the "Start new comment thread" button from the resulting input box](https://meta.codidact.com/uploads/zadu0pmujppjj4j8c2hc0gnzalnw)

Could pressing the "Start new comment thread" button be made to automatically scroll the page to the input box that appears?

Alternatively the buttons could be placed below the existing comment threads rather than above them, then no scrolling would be required as the input box would always appear immediately below the button.

Another alternative would be to make the input box appear above the existing comment threads rather than below them, so it is always immediately below the button.

My preference would be either of the approaches that do not require automatic scrolling, as this has less opportunity to confuse the user.