• A dotted outline that highlights the flex container itself
  • Solid lines which show where the flex items are
  • A background pattern that represents the free space between things

The attractiveness of Flexbox is that the browser can be left by you in charge of creating the layout decisions that are right for you. How much should an element elongate, or should an element wrap to a different line?

Introducing the Flexbox Inspector

When developing JavaScript, both the Console and Debugger are your windows into your code’s execution flow and condition changes. On the past releases we’ve focused on making work better for modern toolchains. Firefox 65 continues this subject.

Additionally, thanks to Patrick Brosset, Nicolas Chevobbe and the whole DevTools staff and friends to helping put together this article.

We’re quite excited for you to try out these two new features and let us know what you believe . But there s more in store.

Flexbox is a effective way to organize and disperse elements in a way that is flexible, on a webpage.
First and foremost, the Flexbox Inspector highlights the elements that compose your own flexbox design: the container, lines and items.
Let’s suppose you’ve mended a flexbox bug thanks to this Flexbox Inspector. You ’ ve made a few edits, to do so. That’s when you re usually faced What did I actually change to make it work? ”.

The post New at Firefox DevTools 65 appeared first on Mozilla Hacks – the Web developer blog.
We hope you’ll love using these tools as far as we and our community loved them.

Console logging is just one element of understanding application state. For problems that are complicated, you want to pause state. Fetching information is generally one of those moments, and it is now made”pausable” with the newest XHR/Fetch Breakpoint from the Debugger.

Open the Inspector on this page, and select the div.masthead.row component. Start looking for the Flex Container panel at the sidebar, and click on the 2 items to see how their sizes are calculated from the browser.

  • Our brand new Flexbox Inspector
  • Smarter JavaScript inspection and debugging

JavaScript getters are very helpful for energetic properties and greatly used in frameworks like vue.js for computed properties. But when you log an object with a getter into the Console, the reference to the method is logged, not its return value. The method does not get invoked as the state of your application may change. As you actually wish to see the worth, now you can manually synchronize getters on items that are logged.
But when you give up control, how can you understand what the browser is actually doing?

To use it at the Console, press F9 on Windows/Linux or Ctrl+R on MacOS and begin typing. You can then use Ctrl+R to proceed to the preceding or Ctrl+S to another result. Eventually, hit return to confirm.

Understand CSS layout like never before

The Flexbox Inspector includes functionality to reveal the browser spread the sizing for a given thing.
As always, we would love to hear your feedback on how DevTools and the browser can enhance.

Thank you

The Collapsing feature works in the Console stack traces for errors and logs, and in the Debugger call stacks.

Reverse lookup your Console history

The layout sidebar now contains a Flex Container section that lists all of the flex items, in addition to supplying information regarding the container .
To achieve this, the browser’s design engine does a lot of items. When everything works like a charm, you don’t even need to be worried about this. But when problems appear on your layout it may feel frustrating, and why components behave a certain way, you may need to know.

DevTools employees was helped by countless contributors by writing patches, submitting bugs and affirming them. Special thanks go to:
Clicking one of these bend items opens the Flex Item segment that displays exactly how the browser calculated the product size.

Smarter JavaScript inspection & debugging

It keeps track of all of the CSS modifications you’ve which means it is possible to keep working as you normally would. After you’re happy, open the Changes tab and see what you did.

After toggled, the highlighter reveals three components:
The diagram at the peak of the flexbox section indicates a fast overview of the measures the browser required to provide the thing its own size.

Invoke getters to inspect the return value

Kudos to Firefox DevTools code contributor Anshul Malik for “Gradually” submitting the patch for this useful feature and for his continuing contributions.

1 way to toggle the highlighter to get a flexbox container is by simply clicking its”flex” badge at the inspector.   This is an effortless method while you re scanning elements to find flex containers. Moreover, you may turn on the highlighter in the flex icon at the CSS rules panel, as well as from the toggle in this layout sidebar’s Flexbox section.
Constructing out the authoring experience in the Console, we’re adding an multi-line editing manner (motivated by Firebug) plus a more powerful autocomplete. Keep a look out for all those features in the most recent release of Firefox Developer Edition.
You may have noticed that people ’ve already been heads down on recent releases to produce the JavaScript debugging encounter rock solid — for breakpoints, stepping, origin maps, functionality, etc.. Continuing to polish and refine and raising the quality bar remains the focus for the team.

Understanding how flex items got their dimensions

You conducted one hour ago in the console, then this is for you if you are tired of beating the arrow key to discover that awesome one-liner. Reverse search is a well known command-line feature that lets you quickly navigate recent commands that match the string.
Among the features and bug fixes which created it in this release to DevTools, We Would like to highlight two
The Firefox DevTools staff is on a mission. We would like you to go from “trying things to really understanding how your browser lays out a page until they operate ”.
We just published Firefox 65 using a number of new developer features which make it even simpler for you to create, inspect and debug the web.
Should youassemble tools and re working with frameworks, then you re used to seeing error stack traces that are really long from the Console. The brand new smarter stack traces identify 3rd party code (such as frameworks) and fall it by default. This considerably lowers the information displayed in the Console and allows you to focus on your own code.
Being able to see how far apart they are and end — and where these start — will go a long way to helping you understand what’s going on.
Download Firefox Developer Edition to get early access to forthcoming tooling and platform.

After the bug fix, keep tabs on changes

It shows your item’s foundation dimensions (either its minimal content dimension or its flex-basis dimensions ), the amount of flexible space that was added (flex-grow) or removed (flex-shrink) from it, and any minimum or maximum defined sizes that restricted the thing from becoming any shorter or longer.


Wherever objects could be inspected, at the Console or Debugger, you’ll see > icons alongside getters. The method will be executed by clicking these and then print the return value.

You’ve already been telling us precisely exactly what your biggest CSS challenges are, and we’ve been listening. We’re now prototyping layout tools for debugging scrollbars, z-indexes that don’t operate, and more tools such as the Flexbox Inspector but for different forms of layouts. We’re planning to make it easier for you to extract your changes in the Changes panel.