Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Beta]: In the Plite pagination example with Facing off, lines at the end of a page overlap while scrolling in Firefox

Aperta
  • Qualcosa non va?
#5,309 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
frontend

Direzione di ricerca

Start in packages/plitejs/src/pagination/, the nearest owner identified in the issue, and reproduce the overlap on the pagination example in Firefox with Facing off. Compare its scrolling behavior with Chromium and WebKit, where the issue was not reproduced. Done when each line keeps its own place while scrolling in Firefox; the cause and relevant test are not identified in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug firefox target:beta triaged

Testing lane

  • Repository: udecode/plate
  • Branch: next
  • Release channel: Beta
  • Exact commit/package version: NOT_ENOUGH_INFO

Summary

On https://beta.platejs.org/examples/plite/pagination with Facing switched off, scrolling down one page in Firefox can draw two lines on top of each other at the end of a page. Another half page of scrolling clears it.

Reproduction

Repro 1: scroll with Facing off, Firefox

An agent ran this in Firefox on natamox's Mac on 2026-10-20 (PT) and took a screenshot.

  1. Open https://beta.platejs.org/examples/plite/pagination with its defaults (Virtualized, Stress pages 990).
  2. Switch Facing off.
  3. Scroll down one page.
  4. Scroll down another half page.

Result: after step 3, the last line of a page shows two lines drawn over each other. In the screenshot, Premirror Milestone 1 test document. This paragraph is intentionally long so word and wrapping and range ownership remain visible inside page frames. Section 6. share one line. After step 4 the page draws normally. The agent saw it once.

natamox retested by hand in Firefox on 2026-10-24 (PT): the overlap still appears while scrolling with Facing off.

Repro 2: Chromium and WebKit

An agent scrolled the same page with Facing off in headless Chromium 149 and WebKit 26.5 (Playwright) on 2026-10-24 and saw no overlap.

Expected

Each line keeps its own place while the page scrolls.

Actual

Two lines at the end of a page are drawn in the same place until the page scrolls on.

Environment

  • Exact next commit/Beta package version: NOT_ENOUGH_INFO. The page does not show its build.
  • Repro 1: Firefox on macOS, 2026-10-20 (PT) and 2026-10-24 (PT). The Firefox version was not noted.
  • Repro 2: Chromium 149.0.7827.55 and WebKit 26.5 (Playwright, headless) on macOS, 2026-10-24. Not reproduced.

Caveat

The cause is not traced. The page layout code in packages/plitejs/src/pagination/ is the nearest owner (inferred). The screenshot also shows the docs sidebar drawn over the page, which is #5254, not this issue.

Evidence

  • Repro 1: the agent's screenshot from 2026-10-20, cropped to remove the browser's bars. The overlapping lines are near the bottom of the page.
Repro 1 — Firefox, /examples/plite/pagination, Facing off

Repro 1 — Firefox, /examples/plite/pagination, Facing off

Related

  • #5253, #5254, #5255 and #5258 are other bugs in this example, with different triggers.
  • #5257: in Safari on /docs/pagination, text shifts when the caret moves, and headings overlap the text during selection. Its page and trigger differ.
Lingua principale
TypeScript
Stelle
16.6k
Fork
993
Merge medio
20h 1m
PR unite (30g)
60

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di udecode/plate

Tutte le issue di udecode/plate

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.