Closed Bug 948713 Opened 11 years ago Closed 6 years ago

Try using multi-line flexbox for PanelUI grid layout

Categories

(Firefox :: Toolbars and Customization, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mconley, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Australis:P-])

I believe we're currently using an unholy mix of XUL flex and CSS3 flex in order to make the Australis PanelUI grid happen.

Recently, bug 702508, giving us multi-line CSS3 flexboxes. I *think* we can leverage that to simplify the grid some - or at the very least, swap out some XUL flex-y business.

It's worth checking to see if this could fix the alignment issue in bug 940379, and bug 924050, since I *think* we chalked that up to a XUL flex + CSS3 flex = confusion problem.
Here's what multi-line flexbox can do:

http://blog.dholbert.org/2013/12/multi-line-flexbox-support-in-nightly.html

Looks familiar.
Just from local fiddling with DOMi, setting display: flex and flex-wrap: wrap #PanelUI-contents *does* seem to fix the Downloads button issue...

It introduces other issues though - like massive elements in the panel when in customize mode, and the wide widgets wrapping around onto two lines, but this might be worth investigating...
Whiteboard: [Australis:P-]
Jared, the reason we're looking at this at all is the issues with some buttons (like the downloads button post-overlay-load, and type="menu-button" buttons, and the placeholders - all of which are PN rather than P-) not being aligned correctly in the panel. We've all looked at that and can't figure out what's causing this, and it's possible switching to "proper" multiline-flex might help fix this, so I'm not convinced this should be P-. Do you disagree?
Flags: needinfo?(jaws)
I marked this as P- because we haven't determined yet if this will fix the issues. It still appears to be in more of an investigative phase.
Flags: needinfo?(jaws)
No more grid layout, so we can close this.
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.