1433897, 1437631, 1456307, 1468910, 1473061, 1474358, 1474364, 1478481, 1486797, 1489333, 1494804, 1497174, 1497312, 1497542, 1499630, 1501226, 1507719, 1507720, 1507728, 1507733, 1507741, 1507752, 1509004, 1509457
The global flexbox tool is being tracked in bug 1409965, but there is too much scope there for shipping purposes. The goal for this reduced meta bug is to only track the few things we will ship in a first version of the flexbox inspector tool. So, a minimal but very polished feature set that will likely only be enabled in nightly to start with, until we add more user value. So, this is milestone 1 so to speak.
I made this one depend only on the bugs part of the scope agreed so far for M1: - simple highlighter for containers, lines and items - rule-view and markup badge toggles - flexbox inspector sidebar These still remain to be defined properly so there will likely be other bugs to be filed. But the important part I think is the lack of support for the following 2 features in M1: - sizing - alignment Those are, in themselves, much bigger and will be tracked in other iterations of the tool.
Martin: does this correspond to our latest discussion? Can we clearly define and capture this M1 scope in the PRD doc?
Summary: [meta] Ship the first simple version of the flexbox inspector → [meta] Ship the first simple version of the flexbox inspector (M1)
Yes, that is what we discussed. Additionally we want to do some style adjustments to be consistent with the grid highlighter. Also, we should re-evaluate the sidebar, but once 1472566 lands it will be more useful. I will try to capture everything in the PRD.
Summary: [meta] Ship the first simple version of the flexbox inspector (M1) → [meta] Ship the first simple version of the flexbox highlighter (M1)
11 months ago
Depends on: 1497174
11 months ago
Depends on: 1497182
Depends on: 1497542
Depends on: 1499668
Depends on: 1505079
Should we close out this meta-bug like we did for the other one (bug 1478396 comment 2)? Looks like we've got 2 remaining open bugs blocking this one, neither of which seem especially bad, and I think this will be riding the trains.
Thanks Daniel, I meant to do this the other day but forgot. Done now.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
[Why is this notable]: It adds an important tool for web authors allowing to investigate Flexbox layout. [Affects Firefox for Android]: no [Suggested wording]: In addition to the earlier introduced Grid Inspector, there is now a Flexbox Inspector. [Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_Flexbox_layouts (should be linked to from "Flexbox Inspector") https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_grid_layouts (should be linked to from "Grid Inspector") Sebastian
You need to log in before you can comment on or make changes to this bug.