[Beta]: On Android Chrome, a tap in the plaintext, markdown-preview and shadow-dom examples shows a caret without a drag handle

Abierto
  • ¿Algo no está bien?
#5,247 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
frontend, web-dev

Línea de trabajo

Start by comparing the Beta examples at /examples/plite/markdown-preview, /examples/plite/plaintext, and /examples/plite/shadow-dom with /examples/plite/schema-reconfiguration, which does show the caret handle on the same phone. Trace what the three affected examples share and check how their editor setup handles Android Chrome caret placement. Done means a tap at each reported text position shows the blue caret handle; the reported schema-reconfiguration example should still work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug mobile target:beta

Testing lane

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

Summary

On Android Chrome, a tap that places the caret in the plaintext, markdown-preview and shadow-dom examples shows the caret but not the blue drop handle under it, so the caret cannot be dragged with the handle. On slatejs.org, the same tap shows the handle. Typing at the caret works on both.

This is not every Beta editor. On the same phone, a tap in https://beta.platejs.org/examples/plite/schema-reconfiguration shows the handle.

Reproduction

Repro 1: /examples/plite/markdown-preview, Android Chrome
  1. Open https://beta.platejs.org/examples/plite/markdown-preview.
  2. Tap the end of the text, after Try it out for yourself!.

The caret appears with no handle. On https://www.slatejs.org/examples/markdown-preview the same tap shows the handle.

Repro 2: /examples/plite/plaintext, Android Chrome
  1. Open https://beta.platejs.org/examples/plite/plaintext.
  2. Tap the end of the text, after just like a <textarea>!.

Same result. On https://www.slatejs.org/examples/plaintext the handle shows.

Repro 3: /examples/plite/shadow-dom, Android Chrome
  1. Open https://beta.platejs.org/examples/plite/shadow-dom.
  2. Tap the end of the text, after nested Shadow DOM..

Same result. On https://www.slatejs.org/examples/shadow-dom the handle shows.

Expected

A tap that places the caret shows Chrome's caret handle, as on slatejs.org.

Actual

The caret has no handle on all three pages. In screenshots taken after the tap, the blue pixels under the caret count 0 on Beta and about 3,960 on slatejs.org.

Environment

  • Exact next commit/Beta package version: NOT_ENOUGH_INFO
  • Device: Xiaomi 14, Android 16, Chrome 154, WeType pinyin keyboard. An agent ran these steps on the real phone on 2026-10-23.
  • Nobody has tried these steps on iPhone or iOS Safari.

Caveat

  • Nobody has traced the cause, or what these three examples share that /examples/plite/schema-reconfiguration does not.
  • The frames come from longer phone recordings of a paste problem on the same pages. Only their second step, the tap, belongs to this issue.

Evidence

  • One image with a crop around the caret for each page, Beta on the left and slatejs.org on the right, taken 1 second into each phone recording, right after the tap.
Repros 1 to 3 — Android Chrome, markdown-preview, plaintext and shadow-dom

Repros 1 to 3 — Android Chrome, markdown-preview, plaintext and shadow-dom

Lenguaje dominante
TypeScript
Estrellas
16.6k
Forks
993
Merge medio
20 h 2 min
PR fusionados (30 d)
62

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de udecode/plate

Todos los issues de udecode/plate

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.