Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Skip to content changes the console page to Overview

Aberta
  • Algo errado?
#421 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@dvd233 já está trabalhando nisso.

Desde 6/10/2026.

  • #422 de @dvd233 — aberto

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
node.js, react, typescript
Domínio
accessibility, frontend

Direção de pesquisa

Read apps/web/src/ConsoleApp.tsx and apps/web/src/lib/console-routes.ts, then inspect the existing web test setup for keyboard and routing coverage. Reproduce the reported fragment behavior and add regression coverage for a non-default route, a parameterized detail page, repeated activation, and Back navigation. Done means Skip to content focuses the main element without changing the route, parameters, or history; linked pull request #422 is already open.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

The console skip link and the application router both use the URL fragment. At main commit 9fa92df0afb170bd57da8314e2a4280aca1fd4ac, ConsoleApp.tsx renders the link with href="#main-content", without an activation handler. Its hashchange listener rereads the route, and consoleViewFromHash() maps that unrecognized fragment to overview.

This means the normal fragment-navigation path changes a non-Overview page to Overview and drops project/resource parameters, rather than just moving focus past the sidebar.

Source-level reproduction

From the checkout root with Node.js 24.19.0:

node --input-type=module <<'JS'
import { consoleViewFromHash } from './apps/web/src/lib/console-routes.ts';
for (const hash of ['#files', '#sessions', '#main-content']) {
  console.log(hash, '=>', consoleViewFromHash(hash));
}
JS

Output: #files => files, #sessions => sessions, #main-content => overview.

The source and routing-helper behavior were verified with AI assistance. This report is not browser-verified.

Proposed scope

Would you accept a focused fix so activating Skip to content focuses the existing main element while preserving the current route, parameters and browser history? The main element already has tabIndex={-1}. I would include keyboard regression coverage from a non-default page and a parameterized detail page, plus repeated activation and Back navigation. No implementation has been made.

Linguagem predominante
Go
Estrelas
210
Forks
29
Merge médio
1h 12min
PRs com merge (30d)
588

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de MiniMax-AI/OpenAgentCore

Todas as issues de MiniMax-AI/OpenAgentCore

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.