Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug] plannotator-* preference cookies pollute every app running on localhost

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

Los mantenedores suelen responder en 1 día

@utpalsinghdev ya está trabajando en esto.

Desde el 26/10/2026.

  • #2188 de @utpalsinghdev — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
backend, web-dev

Línea de trabajo

Read the open pull request #2188 to see the approach already underway, then inspect how Plannotator serves its UI and sets preference cookies. The issue proposes hostname isolation or another opt-in mechanism but does not name files or tests. Done means Plannotator offers a supported way to keep its localhost cookies separate from unrelated local apps.

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

Descripción

bug

Problem

Plannotator stores UI preferences in host-only cookies scoped to localhost (no Domain attribute). Browsers scope cookies by hostname, not port — so every one of these cookies is attached to every origin on localhost, including completely unrelated local development projects.

Evidence

Screenshot from Chrome DevTools on one of my own local projects (a dev server on port 55042 — not plannotator):

Image

The entire cookie list for this origin is plannotator-* entries (annotation-*, diff-*, editor-*, filebro*, grid-*, guide-*, …), dozens of them, all domain localhost, path /, SameSite=Lax. None of them belong to this project.

Impact

  • Every request my local apps make to localhost carries a large Cookie header full of plannotator preferences.
  • DevTools for any localhost project is cluttered with these entries.
  • There is no safe way to clean up: clearing cookies by hostname wipes data for all local apps at once, not just plannotator.

Request

Provide a supported way to isolate plannotator's storage from other localhost apps — e.g. serving on a dedicated hostname (such as plannotator.localhost, which browsers resolve to 127.0.0.1 per RFC 6761) or another opt-in mechanism, so its cookies don't leak into unrelated local projects.

Environment

  • plannotator: v0.28.20 (latest release at the time of writing: v0.28.23 — not verified against it)
  • OS: macOS Sonoma 14.3.1 (Apple M3 Pro)
  • Browser: Chrome 156
  • Agent: Claude Code 2.1.295
Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
649
Merge medio
6 h
PR fusionados (30 d)
514

Preparar el entorno

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 backnotprop/plannotator

Todos los issues de backnotprop/plannotator

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.