Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Answer shortcut vanishes on a narrow frame

Ouverte
  • Quelque chose ne va pas ?
#1,323 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
52/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
cli

Piste de recherche

Start by locating taskPaneCols, taskPaneOpen, taskPaneKey, and taskRecordAnswer, then run the replication recipe in a terminal narrower than 110 columns. Check the tasks list and the record card using the digit and enter. Done means the narrow list either accepts the answer key directly or visibly tells the user how to answer, verified end to end on the real surface.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:chat bug sev:papercut

What happens

Below a frame width of 110 cells the tasks list draws no side pane, and with no pane the answer keys the pane offers are not bound. taskPaneCols returns zero under the floor, taskPaneOpen reports false from it, and taskPaneKey returns early on !a.taskPaneShowing(), so a digit that names an answer does nothing from the list.

What is NOT wrong, checked before filing

The answer road still exists at any width. enter from the list opens the record card, and the card reaches the same door (taskRecordAnswer) that the pane reaches, by the comment's own statement that a second loop over the options there would be a second chance for the two to disagree about what 1 means.

So this is one extra keystroke on a narrow terminal, not an unanswerable question. An earlier reading of this as "the page has no door below 110 columns" was wrong and is corrected here.

Why it is still worth deciding

  1. The verb line that advertises the keys is drawn by the pane, so on a narrow frame a person is not told the shortcut is unavailable; it is simply absent. Nothing says "press enter to answer".
  2. Nobody has established whether the record card itself renders usefully below 110 cells. That is unverified and is the question that decides whether this is cosmetic or real.

The decision wanted

Either: accept the floor, and make the narrow list say how to answer, so the absence is announced rather than silent.

Or: bind the answer keys on the list itself at any width, so the shortcut does not depend on a layout choice.

The first is smaller and consistent with the floor's stated reasoning, which is that under 110 cells a split buys a preview by making the thing previewed unreadable.

Replication

NOT YET RUN. Recipe a stranger can execute: open the tasks place in a terminal narrower than 110 columns with a row whose work is waiting on an answer, and press the digit the wide frame would accept. Then press enter and the same digit on the card.

Acceptance

End to end, at a frame under the floor: the list either accepts the answer key directly, or draws a line naming the key that does. Asserted on the real surface, not on a width helper.

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
9 h 44 min
PR mergées (30 j)
775

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.