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

Form update uses incorrect target on reconnect

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
elixir
Área
backend

Línea de trabajo

Start by creating the simplified reproducible project described in the issue, using Surface v0.6.1, LiveView v0.16.4, and the shown component hierarchy. Trace reconnect handling and the handle_event/3 target resolution while the tab is backgrounded; done means reconnecting no longer repeatedly calls MyLiveComponent.handle_event/3 instead of the LiveView handler.

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

Descripción

I have a component hierarchy that looks something like this:

MyLiveView
  -> MyLiveComponent
    -> MyFormComponent
      -> <Surface.Components.Form change={"update", target: :live_view} ... />

This works great on the golden path, handle_event/3 is called on the LiveView as expected.

However, if the tab has to reconnect to my app while the tab is in the background, such as in the following scenarios:

  1. Put the tab in the background (i.e. open some other tab as the active tab)
  2. Restart the server

or

  1. Put the tab in the background (i.e. open some other tab as the active tab)
  2. Close computer (goes to sleep)
  3. Open computer later

My app tab (which is not the active tab in Chrome) will reconnect and attempt to call handle_event on MyLiveComponent instead of on MyLiveView, over and over again, indefinitely.

The (redacted) error I see in my console is:

** (UndefinedFunctionError) function MyLiveComponent.handle_event/3 is undefined or private

If I then click on the tab and make it the active tab, it seems to do something slightly different and is able to re-establish the correct target and figure it out.

I wasn't sure if this was a dev-only issue, but I recently launched to the public and found that it indeed affects production as well, as AppSignal is showing 1,800 errors per hour, per user.

I'm going to work on making a simplified, reproducible project once I have a minute, but I'm not familiar with the internals of Surface or LiveView and wondered if anyone had any feedback on where I might start looking for the problem, or a workaround.

Surface: v0.6.1
LiveView: v0.16.4
Elixir: v1.12.2
Chrome: 96.0.4664.110

Lenguaje dominante
Elixir
Estrellas
2.1k
Forks
146
Sin PR fusionados en 30 d

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 surface-ui/surface

Todos los issues de surface-ui/surface

Issues similares

Más issues de Elixir

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.