drop down for pages in a collection
Bug #1501185 reported by
shanen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
High
|
Unassigned | ||
| 15.10 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Mahara 15.04
Wishlist item
Hi Guys. For sometime i have thought that aesthetics and usability suffers due to the tabs navigation approach, but only when collections have multiple pages and the tabs don't fit. Eg our templates have 15 pages in some disciplines and having a block of tabs (expanded) looks very clunky.
There may be other ways to approach what to do with tabs that don't fit on the screen. For example putting additional tabs in a drop down list. This approach is responsive but also follows convention of having more options (pages ) in a drop down.
There could be other ways to create an elegant solution?
Cheers. Well done on 15.10.
Revision history for this message
| Robert Lyon (robertl-9) wrote | #1 |
| Changed in mahara: | |
| milestone: | none → 15.10.0 |
| status: | New → Fix Committed |
| importance: | Undecided → High |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The idea of having a collection's page titles is the approach we are adding to 15.10 version of Mahara.
Instead of having all the tabs there will be layout similar to this:
'Previous page' 'Navigate to page:' [dropdown] 'Next page'
Where the dropdown contains the titles of the pages in the collection.
I don't believe this feature will be backported to earlier version due to the code relying on bootstrap features.