update frontend when db changes

NEW
Unassigned

Status

Release Engineering
Balrog: Frontend
P3
normal
2 years ago
a year ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [lang=js][lang=python])

(Reporter)

Description

2 years ago
Something that came up in bug 1113689 is that the Balrog frontend requires a reload to pick up changes to the db. This means that if you're doing things in multiple tabs, or multiple people are doing things at once, you can easily hit outdated data errors. This is frustrating and probably unnecessary in the modern world where servers can notify clients of changes.

I'm not knowledgable enough to know exactly how to fix this, but it would be great to have.
(Reporter)

Comment 1

a year ago
This probably requires significant changes to the frontend and backend, eg: using PUSH notifications.
Priority: -- → P3
Whiteboard: [lang=js][lang=python]
You need to log in before you can comment on or make changes to this bug.