Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software deployments.

1. Firefox 62.0.3
2. Firefox 62

• Hello, developers of Firefox! I've been using this browser for 10 years and I've always liked it. But the last update of 62.0 is very, very bad, because the 'Properties' window of the bookmarks now looks awful and the 'Description' field has disappeared.
• Google Chrome is a fast, simple, and secure web browser, built for the modern web. Speed Chrome is designed to be fast in every possible way. It's quick to start up from your desktop, loads web pages in a snap, and runs complex web applications lightning fast.

Opening Settings

Beginning with Firefox 62, the icon to open Developer Tools settings has been moved into a menu accessed by clicking/touching ... (the ellipsis) on the right of the tab.

The menu includes settings to control the location of the Developer Tools. You can choose between the default setting at the bottom of the windows, or move the tools to the left or right side of the screen. These settings are particularly useful if you have a widescreen monitor. You can also choose to open the tools in a separate window.

Show split console adds a section at the bottom of the tools showing the console. It makes visible the command line and one or two lines of the console output.

The rest of the settings are on the Developer Tools Settings Pane. To see the settings, open any of the Developer Tools, and then:

• click the 'Settings' command in the menu:
• or press F1 to toggle between the active tool and the Settings pane

The Settings pane looks something like this:

Categories

Default Firefox Developer Tools

This group of checkboxes determines which tools are enabled in the toolbox. New tools are often included in Firefox but not enabled by default.

Available Toolbox Buttons

This group of checkboxes determines which tools get an icon in the Toolbox's toolbar.

As of Firefox 62, if the option to 'Select an iframe as the currently targeted document' is checked, the icon will appear in the toolbar while the Settings tab is displayed, even if the current page doesn't include any iframes.

Note that in Firefox 52 we removed the checkbox to toggle the 'Select element' button. The 'Select element' button is now always shown.

Themes

This enables you to choose one of two themes.

• There's a light theme, which is the default:

• A dark theme (the default on Firefox Developer Edition):

Common preferences

Settings that apply to more than one tool. There's just one of these:

Enable persistent logs

A setting to control whether or not the Web Console and Network Monitor clear their output when you navigate to a new page.

If Common Preferences is not included in the Settings, Web Console logs can be persisted by using the 'about:config' url in browser address bar, searching for: 'devtools.webconsole.persistlog' then toggling this value to true

Inspector

Show browser styles

A setting to control whether styles applied by the browser (user-agent styles) should be displayed in the Inspector's Rules view. Note that this setting is independent of the 'Browser styles' checkbox in the Inspector's Computed view.

Truncate DOM attributes

By default, the Inspector truncates DOM attributes that are more than 120 characters long. Uncheck this box to prevent this behavior. This setting works by toggling the about:config preference 'devtools.markup.collapseAttributes'. To change the threshold at which attributes are truncated, you can edit the about:config preference 'devtools.markup.collapseAttributeLength'.

Default color unit

A setting to control how colors are represented in the inspector:

• Hex
• HSL(A)
• RGB(A)
• color name
• As authored.

Enable layout panel

Enable the experimental layout panel. This setting only exists in Firefox Nightly.

Web Console

Debugger

Style Editor

Screenshot Behavior

Editor Preferences

Preferences for the CodeMirror source editor, which is included in Firefox and used by several developer tools, including Scratchpad and the Style Editor.

Detect indentation

Auto-indent new lines based on the current indentation.

Autoclose brackets

Determines whether typing an opening character like [ or { will cause the editor to insert the matching closing character ] or } for you.

Indent using spaces

When checked, indentation will be performed using spaces, when off, the editor will use tabs instead.

Tab size

The frequency of tab stops in the editor. Select 2, 4, or 8.

Keybindings

Choose the default CodeMirror keybindings or keybindings from one of several popular editors:

• Vim
• Emacs
• Sublime Text

Advanced settings

Show Gecko platform data

A setting to control whether or not profiles should include Gecko platform symbols.

Disable HTTP Cache

Disable the browser HTTP cache to simulate first-load performance in all tabs that have the Toolbox open. This setting persists, meaning that if it is set, caching will be disabled whenever you reopen the devtools. Caching is re-enabled when the devtools are closed. Note that service workers are not affected by this option.

Disable JavaScript

Reload the current tab with JavaScript disabled.

Enable Service Workers over HTTP

Enable Service Worker registrations from insecure websites.

Enable browser chrome and add-on debugging toolboxes

Enable you to use developer tools in the context of the browser itself, and not only web content.

Enable remote debugging

Enable the developer tools to debug remote Firefox instances.

Enable worker debugging

Enable a panel within the debugger to debug workers.

Note: This option got removed from the UI in Firefox 56, because this version ships with a new Debugger UI, but it can still be enabled for the old UI by setting the preference devtools.debugger.workers to true.

Firefox 62, which lands in general release this week, adds support for Variable Fonts, an exciting new technology that makes it possible to create beautiful typography with a single font file. Variable fonts are now supported in all major browsers.

What are Variable Fonts?

Font families can have dozens of variations: different weights, expanded or condensed widths, italics, etc. Traditionally, each variant required its own separate font file, which meant that Web designers had to balance typographic nuance with pragmatic concerns around page weight and network performance.

Compared to traditional fonts, variable fonts contain additional data, which make it possible to generate different styles of the font on demand. For one example, consider Jost*, an open-source, Futura-inspired typeface from indestructible type*. Jost* comes in nine weights, each with regular and italic styles, for a total of eighteen files.

Jost* also comes as a single variable font file which is able to generate not only those same eighteen variations, but also any intermediate weight at any degree of italicization.

Design Axes

Jost* is an example of a “two-axis” variable font: it can vary in both weight and italics. Variable fonts can have any number of axes, and each axis can control any aspect of the design. Weight is the most common axis, but typographers are free to invent their own.

One typeface that invented its own axis is Slovic. Slovic is a Cyrillic variable font with a single axis, style, that effectively varies history. At one extreme, characters are drawn similarly to how they appear in 9th century manuscripts, while at the other, they adopt modern sans-serif forms. In between are several intermediate styles. Variable font technology allows the design to adapt and morph smoothly across the entire range of the axis.

The sky’s the limit! To see other examples of variable fonts, check out v-fonts.com and Axis Praxis.

Better Tools for Better Typography on the Web

Great features deserve great tools, and that’s why we’re hard at work building an all new Font Editor into the Firefox DevTools. Here’s a sneak peek:

You can find the Font Editor as a panel inside the Page Inspector in the Dev Tools. If you have enough space on your screen, it’s helpful to enable 3-pane mode so you can see the DOM tree, CSS Rules, and Font Editor all side-by-side.

When you click on an element in the DOM tree, the Font Editor updates to show information about the selected element’s font, as well as tools for editing its properties. The Font Editor works on all fonts, but really shines with variable ones. For instance, the weight control subtly changes from stepped slider to continuous one in the presence of a variable font with a weight axis.

Similarly, each design axis in a variable font gets its own widget in the editor, allowing you to directly customize the font’s appearance and immediately see the results on your page.

The new Font Editor will arrive with Firefox 63 in October, but you can use it today by downloading Firefox Nightly. Let us know what you think! Your feedback is an essential guide as we continue to build and refine Firefox’s design tools.

Firefox 62.0.3

Editor’s note: Attention MacOS users — variable fonts require MacOS 10.13+

About Dan Callahan

Firefox 62

Engineer with Mozilla Developer Relations, former Mozilla Persona developer.