Using main_side with no entries renders a ghost box

Bug #420778 reported by Brad Crittenden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

If a page has an some global actions that are only conditionally enabled for, say, owners and admins, and they are put in the side slot, then when the page is viewed by an unprivileged person those controls aren't rendered but there is a thin grey box where the side portlet should be.

Choosing between main_side and main_only is not something easily done conditionally. Can this behavior be fixed?

See https://launchpad.dev/ubuntu/+mirror/archive-mirror2

Tags: lp-web
affects: launchpad → launchpad-registry
Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: New → Triaged
importance: Undecided → Low
affects: launchpad-registry → launchpad-foundations
Changed in launchpad-foundations:
assignee: Curtis Hovey (sinzui) → nobody
Revision history for this message
Curtis Hovey (sinzui) wrote :

The milestone template resolved this by adding a CSS rule to the page. Each page needs to write a rule to identify that nothing in the menu will render. CSS does not support rules based on children, and the menu infrastructure does not tell us if any links will render

affects: launchpad-foundations → launchpad-web
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.