I'm this close to archive.

Abierto
#367 2 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 5 días

@WebReflection ya está trabajando en esto.

Desde el 7/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

help wanted

This is likely the only real issue I have with this project.

Folks, if you ask me to improve legacy methods such as live-collections, you are telling me you didn't read anything about this project and you are not contributing at all if not by forcing me to kill it.

I do not care about stuff documented and described as legacy support, meaning if your getElementsByTagNames('*') doesn't work, I don't care, and so it goes for anything that is a live collection which is documented to not work and you should stop writing code that trust any of those legacy methods ... I'd like to say "it's not you, it's me" ... but honestly "it's you, not me", because if you don't read the premises of this project and you just keep piling up issues when my last quest was for maintainers and contributors and nobody showed up, 'cause nobody is paying me to maintain this project and I am not using this daily neither, I am afraid you can use your noisy tokens to reproduce and replicate by all means this project in Rust, directly WASM, whatever it fits your bill because I have enough of irrelevant noise about a genuine project with a scope and goal most latest "issues reporters" didn't dare to even read is extremely disappointing from an OSS community driven project side of affairs.

If you never used AI to create your issue, use YE instead (Your Eyes - apologies for blind contributors, I know you fully understand not reading/understanding means, that's my current curse) to understand what we do here, how we do that, what's the goal and how we can improve.

If you are here pretending to contribute with tons of stuff nobody should need in 2026, fork this project and leave me alone, can you?

Thank you all for helping me out not killing this project already, 'cause I am doing my best out of my non-existent free time to move forward with stuff that matters (see latest CSS improvements) but I am not willing to stress myself out of your poor duty as OSS contributor.

Regards.

Lenguaje dominante
HTML
Estrellas
2.1k
Forks
117
Merge medio
4 d 13 h
PR fusionados (30 d)
2

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 WebReflection/linkedom

Todos los issues de WebReflection/linkedom

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.