Closed Bug 1003845 Opened 11 years ago Closed 11 years ago

[tarako] Support Site and Homepage buttons should be disabled when offline

Categories

(Marketplace Graveyard :: General, defect, P2)

Other
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: vcarciu, Assigned: spasovski)

References

Details

tarako build identifier: 20140331101634 connectivity used: Offline(Airplane mode) noticed on: dev (latest build) app used for test: YouTube steps to reproduce: 1. Launch the latest marketplace-dev packaged app 2. Open YouTube app 3. Press Support Site button expected behavior: Support URL opens in the browser and the browser will show a message that you need to be online observed behavior: Nothing happens reproducible?: yes ashes: behavior seen on regular marketplace using inari/hamachi: yes/no
Same issue for Homepage button
Summary: [tarako] Support Site button is not working when offline → [tarako] Support Site and Homepage buttons are not working when offline
We decided to disable buttons when the user isn't online, but the appearance of the button should reflect that it's disabled. So I would say that the expected behavior is not correct, but the button state should also imply that it won't work anyway.
Flags: needinfo?(vcarciu)
In this case, I will update the summary and change the STRs : steps to reproduce: 1. Launch the latest marketplace-dev packaged app 2. Open YouTube app expected behavior: Support Site and Homepage buttons are disabled observed behavior: Buttons are enabled
Flags: needinfo?(vcarciu)
Summary: [tarako] Support Site and Homepage buttons are not working when offline → [tarako] Support Site and Homepage buttons should be disabled when offline
Assignee: nobody → dspasovski
Priority: -- → P3
We're no longer disabling buttons when the user is offline. We're instead displaying a notification to the user that they need to be online. See bug 1001055 for similar treatment.
Priority: P3 → P2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.