Closed Bug 982699 Opened 6 years ago Closed 6 years ago

Use super-toast confirmation on adding new Home Panel

Categories

(Firefox for Android :: General, defect)

ARM
Android
defect
Not set

Tracking

()

RESOLVED INVALID

People

(Reporter: liuche, Unassigned)

References

(Blocks 1 open bug)

Details

Super-toast will give us the option to take the user to the new panel, or continue whatever they were doing.
Blocks: lists
Ian, any string suggestions for this?

'<New panel name>' has been added | View
I worry about this, since we don't really know if there's any data to show at this point. Most of the home panel examples I've seen install the panel before there's actually any data around (and I don't trust panels to fill in content in it arrives while they're showing). Then again, showing this 5 minutes after you create a panel will likely be confusing as well. This will be trickier than it sounds.
(In reply to Wesley Johnston (:wesj) from comment #2)
> I worry about this, since we don't really know if there's any data to show
> at this point. Most of the home panel examples I've seen install the panel
> before there's actually any data around (and I don't trust panels to fill in
> content in it arrives while they're showing). Then again, showing this 5
> minutes after you create a panel will likely be confusing as well. This will
> be trickier than it sounds.

I think this is a separate problem to solve, and goes back to the issue of letting an add-on know when it's been installed. In our demo add-ons, we've just been auto-installing the panel for the user when the add-on is installed, but this is about a user installing the panel from the panel picker activity.

I think part of the solution here will be having sensible empty views for the panels, so that they don't look totally broken, as well as fixing SQLiteBridge to update the cursor when the data changes.
If this is something we want for 30, we'll need to do it ASAP. However, I don't think this is a really big deal for now, since adding panels from the picker won't be a main use-case for 30, and this is just an enhancement, not a critical issue with the flow.
Flags: needinfo?(ibarlow)
Yeah, probably not critical for 30
Flags: needinfo?(ibarlow)
We removed the "Add panel" item in settings, so this isn't an issue anymore.

There is still the issue of whether or not to take the user to a new panel when it is installed by an add-on, but I think we can leave that up to add-on developers to handle.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.