Chromium: excessive layout time with many math previews due to unused CSS anchor

Abierto Apto para principiantes
#3,098 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
84/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
react, typescript

Línea de trabajo

Comienza en packages/core/src/editor/Block.css e inspecciona la declaración anchor-name de .bn-preview-container; el issue informa de que no existe ningún consumidor del anchor y de que eliminarla elimina el coste de layout de Chromium. Reproduce el fixture 500-inline-formula proporcionado, compara los resultados de Chromium Performance con y sin la declaración y confirma que todas las previews siguen renderizándose tanto en modo editable como de solo lectura.

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

Descripción

What’s broken?

Rendering 500 official inline math previews in Chromium spends about 17.6 seconds in layout, including with editable={false}. Every .bn-preview-container receives anchor-name: --bn-source-popup-anchor in packages/core/src/editor/Block.css, although the current popup positioning does not consume this anchor.

Removing that declaration reduces layout to about 0.43 seconds with the same content and DOM.

What did you expect to happen?

Closed source previews should not incur CSS-anchor layout overhead when popup positioning does not use anchors.

Steps to reproduce
  1. In a React app with @blocknote/core, @blocknote/react, @blocknote/mantine, and @blocknote/math-block, render this component:
import { BlockNoteSchema, defaultBlockSpecs, defaultInlineContentSpecs } from "@blocknote/core";
import { useCreateBlockNote } from "@blocknote/react";
import { BlockNoteView } from "@blocknote/mantine";
import { createReactInlineMathSpec } from "@blocknote/math-block";
import "@blocknote/mantine/style.css";

const schema = BlockNoteSchema.create({
  blockSpecs: defaultBlockSpecs,
  inlineContentSpecs: {
    ...defaultInlineContentSpecs,
    math: createReactInlineMathSpec(),
  },
});
const initialContent = Array.from({ length: 25 }, (_, row) => ({
  type: "paragraph",
  content: Array.from({ length: 20 }, (_, col) => [
    { type: "text", text: " text ", styles: {} },
    { type: "math", content: `x_{${row * 20 + col}}^2 + y^2 = z^2` },
  ]).flat(),
}));

export default function App() {
  const editor = useCreateBlockNote({ schema, initialContent });
  return <BlockNoteView editor={editor} editable={false}
    formattingToolbar={false} sideMenu={false} slashMenu={false} />;
}
  1. Serve a production build and record page load in Chromium's Performance panel.
  2. Add .bn-preview-container { anchor-name: none !important; } as a diagnostic override and reload. Layout time drops substantially; all 500 formulas remain rendered.
  3. Repeat with editable={true}; the same issue occurs.
BlockNote version

Reproduced on 0.54.0 and current source at 835fabf86ef26c9932075ab47f3d03cf900f276b.

Environment

Chromium 151.0.7922.137, Linux, AMD Ryzen 7 5800X. Production React/Vite fixture, 1280×900 viewport, no CPU throttling.

Additional context

Current-source production builds, three runs per cell; median cumulative CDP LayoutDuration through editor/font readiness:

500 inline formulas Original Declaration removed
Editable 17.610 s 0.437 s
Read-only 17.684 s 0.427 s

Median readiness improves from 18.51 to 1.28 seconds in editable mode. The same trigger also reproduces with official block math. No position-anchor, anchor(), or anchor-size() consumer exists in the inspected source; popups currently use absolute positioning.

Contribution
  • I'd be interested in contributing a fix for this issue
Lenguaje dominante
TypeScript
Estrellas
10.2k
Forks
772
Merge medio
3 d 11 h
PR fusionados (30 d)
17

Guía de contribución

Abrir la guía de contribución

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 TypeCellOS/BlockNote

Todos los issues de TypeCellOS/BlockNote

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.