Closed Bug 1203337 Opened 10 years ago Closed 9 years ago

lack of difference between ui-showcase "error notification" and "error notification - authenticated" views

Categories

(Hello (Loop) :: Client, defect, P3)

Product:
Hello (Loop)
Component:
Client
Type:
defect
Points:
2

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: crafuse, Unassigned)

References

Details

(Whiteboard: [investigation][tech-debt])

User Story

See difference between ui-showcase "error notification" and "error notification - authenticated" views.

Acceptance criteria:

* should see visual difference between the two notification types.

Technical checklist:

* CSS change or not being set to correct location.
No description provided.
Iteration: --- → 43.3 - Sep 21
Points: --- → 2
User Story: (updated)
Priority: -- → P2
Blocks: 1192372
Blocks: 1179193
investigate to find out if product bug - if not, delay. if yes - take.
Assignee: nobody → dmose
Rank: 19
Priority: P2 → P1
Whiteboard: [investigation][tech-debt]
There are multiple things going on here. There is a ui-showcase bug that uses the errNotification string "Could Not Authenticate" for the "Error Notification - authenticated" view, which is confusing. Trivial fix, and not a product issue. There is an (occasional on my machine) race condition, probably in the ui-showcase, where the error bar gets removed from the "Error Notification" view, perhaps PanelView.updateServiceErrors after PanelView._serviceErrorToShow, perhaps because the fake mozLoop in use in the ui-showcase does not have the "errors" property set correctly. This second needs more investigation, but there's currently no strong reason to believe this is a product bug, so dropping the priority.
Assignee: dmose → nobody
Rank: 19 → 38
Priority: P1 → P3
Iteration: 43.3 - Sep 21 → ---
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.