Closed Bug 1264324 Opened 8 years ago Closed 5 years ago

update frontend when db changes

Categories

(Release Engineering Graveyard :: Applications: Balrog (frontend), defect, P3)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (frontend)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

Details

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

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.
This probably requires significant changes to the frontend and backend, eg: using PUSH notifications.
Priority: -- → P3
Whiteboard: [lang=js][lang=python]

Mass closure of old Balrog UI bugs. We've built a new UI in https://github.com/mozilla-frontend-infra/balrog-ui, and any issues which are still valid should be filed as Issues there.

I think https://github.com/mozilla-frontend-infra/balrog-ui/issues/6 covers most of this.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.