Fallback for a broken image disappears after a few seconds #99

New issue

Open

opened 2020-11-19 07:44:03 +00:00 by eugenijm · 1 comment

eugenijm commented

2020-11-19 07:44:03 +00:00

Member

Initially it is rendered correctly

But after a few seconds:

More specifically, it disappears on the next feed poll (increasing the polling interval makes it stay longer).

Initially it is rendered correctly ![Screen_Shot_2020-11-19_at_10.44.30_AM](/attachments/86820ca4-cbd5-4bcd-a2c6-3e8c281d0e63) But after a few seconds: ![Screen_Shot_2020-11-19_at_10.44.17_AM](/attachments/90e52d79-e65f-4e05-bc5c-d8ea4c4bc328) More specifically, it disappears on the next feed poll (increasing the polling interval makes it stay longer).

Screen_Shot_2020-11-19_at_10.44.30_AM.png

118 KiB

Screen_Shot_2020-11-19_at_10.44.17_AM.png

116 KiB

eugenijm commented

2020-11-21 12:34:59 +00:00

Author

Member

Update: this appears to be caused by an internal arrayContentDidChange call that is triggered on every poll. For some reason this discards the fallback image, more specifically the error class that is dynamically added via with-load-error-states to the element. This is a bit strange especially if the error class being discarded means the entire component is being re-rendered on poll. Investigating this further

Update: this appears to be caused by an internal `arrayContentDidChange` call that is triggered on every poll. For some reason this discards the fallback image, more specifically the error class that is dynamically added via `with-load-error-states` to the element. This is a bit strange especially if the `error` class being discarded means the entire component is being re-rendered on poll. Investigating this further