Closed Bug 942293 Opened 11 years ago Closed 4 years ago

[meta] Support for additional layout and view types


(Firefox for Android Graveyard :: Awesomescreen, defect)

Not set


(Not tracked)



(Reporter: Margaret, Unassigned)



(Keywords: meta)

In bug 862805, we're assuming the list data is just a list of sites, but there can be different kinds of list data (e.g. reading lists, pictures, videos).

We shouldn't expand the scope of this too much for v1, but we should make sure our architecture supports different types of displays for the list data. As part of this we could try to implement one alternate type of list display, e.g. a "text preview list" that displays paragraph previews of reading list items.
Depends on: 942887
Depends on: 942888
Depends on: 942889
Depends on: 942891
Depends on: 942894
Depends on: 942895
Depends on: 942897
Depends on: 942898
The world has changed since this bug was filed. Bug 959777 lays the foundation for adding different kinds of views to third-party panels, so let's just use this bug to track the different kinds of views we want to support.

With our current implementation, a panel has one layout, and that layout can contain multiple views. LayoutType and ViewType are used to specify the different types of layouts and views.
Summary: Create different types of views for list data → [meta] Support for additional layout and view types
Depends on: 942295
No longer depends on: 942895
No longer depends on: 942891
No longer depends on: 942894
No longer depends on: 942898
Depends on: 972448
Keywords: meta
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.