Could log viewer's full screen mode be full window mode instead?

Aberta
#24 2 comentários 1 reação 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
react, typescript
Domínio
frontend

Direção de pesquisa

Start by reviewing the log viewer's existing expand and browser full-screen behavior. Determine how a window-contained viewing mode would work across the modal, side-panel, and tab contexts described in the issue; done means users can enlarge the viewer without leaving the browser window or interrupting normal tab and window workflows.

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

Descrição

The OpenShift log viewer and now this log viewer both offer an expand feature, which uses the browser full screen mode to increase the size and offer more screen real estate. This is really frustrating as someone who always has multiple tabs and multiple windows open, I never want that on a big monitor. On Mac there's an animation to open it, and again to close it, and I have to close it to go do anything other than look at the log.
We use the OpenShift based log viewer in RHTAP today (part of HAC) in a variety of spots (modal, side panel, tab, etc), and in cases where I want it to be bigger and not have to scroll vertically or horizontally as much, I just want it to be bigger within my window, so I can keep my normal workflow. I'm assuming we may move over to this new implementation at some point, so if there's something we can do here to change that behavior, or offer another viewing mode alongside fullscreen that does this, that gives us another reason to move when its ready.

Is this something you'd consider?

Linguagem predominante
TypeScript
Estrelas
34
Forks
19
Métricas de merge de PRs
Nenhum PR com merge em 30d

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 patternfly/react-log-viewer

Todas as issues de patternfly/react-log-viewer

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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