Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.chrome.com/docs/devtools/css/reference/ below:

CSS features reference | Chrome DevTools

Discover new workflows in this comprehensive reference of Chrome DevTools features related to viewing and changing CSS.

See View and change CSS to learn the basics.

The Elements panel of DevTools lets you view or change the CSS of one element at a time.

On the screenshot, the h1 element that's highlighted blue in the DOM Tree is the selected element. To the right, the element's styles are shown in the Styles tab. To the left, the element is highlighted in the viewport, but only because the mouse is hovering over it in the DOM Tree.

See View an element's CSS for a tutorial.

There are many ways to select an element:

• In your viewport, right-click the element and select Inspect.
• In DevTools, click Select an element or press Command+Shift+C (Mac) or Control+Shift+C (Windows, Linux), and then click the element in the viewport.
• In DevTools, click the element in the DOM Tree.
• In DevTools, run a query like document.querySelector('p') in the Console, right-click the result, and then select Reveal in Elements panel.

Use the Elements > Styles and Computed tabs to view CSS rules and diagnose CSS issues.

The Styles tab displays links in various places to various other places, including but not limited to:

• Next to CSS rules, to style sheets and CSS sources. Such links open the Sources panel. If the style sheet is minified, see Make a minified file readable.
• In the Inherited from ... sections, to parent elements.
• In var() calls, to custom property declarations.
• In animation shorthand properties, to @keyframes.
• Learn more links in documentation tooltips.
• And more.

Here are some of them highlighted:

Links may be styled differently. If you're not sure if something is a link, try clicking it to find out.

Elements > Styles shows tooltips with useful information when you hover over specific elements.

To see a tooltip with a short CSS description, hover over the property name in the Styles tab.

Click Learn more to go to an MDN CSS Reference on this property.

To turn the tooltips off, check Don't show.

To turn them back on, check Settings > Preferences > Elements > Show CSS documentation tooltip.

Hover over a selector to see a tooltip with its specificity weight.

Hover over a --custom-property to see its value in a tooltip.

The Styles tab recognizes many kinds of CSS issues and highlights them in different ways.

See Understand CSS in the Styles tab.

The Styles tab shows you all of the rules that apply to an element, including declarations that have been overridden. When you're not interested in overridden declarations, use the Computed tab to view only the CSS that's actually being applied to an element.

1. Select an element.
2. Go to the Computed tab in the Elements panel.

Check the Show All checkbox to see all properties.

See Understand CSS in the Computed tab.

Use the Computed tab. See View only the CSS that's actually applied to an element.

Check the Show All checkbox in the Computed tab. See View only the CSS that's actually applied to an element.

Alternatively, scroll the Styles tab and find sections named Inherited from <element_name>.

At-rules are CSS statements that let you control CSS behavior. Elements > Styles shows the following at-rules in dedicated sections:

• @property
• @supports
• @scope
• @font-palette-values
• @position-try

The @property CSS at-rule lets you define CSS custom properties explicitly and register them in a style sheet without running any JavaScript.

Hover over the name of such property in the Styles tab, to see a tooltip with the property's value, descriptors, and a link to its registration in the collapsible @property section at the bottom of the Styles tab.

To edit an @property rule, double-click its name or value.

The Styles tab shows you the @supports CSS at-rules if they are applied to an element. For example, inspect the following element:

If your browser supports the lab() function, the element is green, otherwise it's purple.

The Styles tab shows you CSS @scope at-rules if they are applied to an element.

The new @scope at-rules are a part of the CSS Cascading and Inheritance Level 6 specification. These rules allow you to scope CSS styles, in other words, explicitly apply styles to specific elements.

View the @scope rule in the following preview:

1. Inspect the text on the card in the preview.
2. On the Styles tab, find the @scope rule.

In this example, the @scope rule overrides the global CSS background-color declaration for all <p> elements inside elements with a card class.

To edit the @scope rule, double-click it.

The @font-palette-values CSS at-rule lets you customize the default values of the font-palette property. Elements > Styles shows this at-rule in a dedicated section.

View the @font-palette-values section in the next preview:

1. Inspect the second line of text in the preview.
2. In Styles, find the @font-palette-values section.

In this example, the --New font palette values override the default ones of the colored font.

To edit your custom values, double-click them.

The @position-try CSS rule along with the position-try-options property lets you define alternative anchor positions for elements. To learn more, see Introducing the CSS anchor positioning API.

Elements > Styles resolves and links the following:

• position-try-options property values to a dedicated @position-try --name section.
• position-anchor property values and anchor() arguments to the corresponding elements with popovertarget attributes.

Inspect the position-try-options values and @position-try sections in the next preview:

1. In the preview, open the submenu, that is, click YOUR ACCOUNT then STOREFRONT.
2. Inspect the element with id="submenu" in the preview.
3. In Styles, find the position-try-options property and click its --bottom value. The Styles tab takes you to the corresponding @position-try section.
4. Click the position-anchor value link or the same anchor() arguments. The Elements panel selects the element with the corresponding popovertarget attribute and the Styles tab shows the element's CSS.

To edit values, double-click them.

To view the box model of an element, go to the Styles tab and click the Show sidebar button in the action bar.

To change a value, double-click on it.

Use the Filter box on the Styles and Computed tabs to search for specific CSS properties or values.

To also search inherited properties in the Computed tab, check the Show All checkbox.

To navigate the Computed tab, group the filtered properties in collapsible categories by checking Group.

If you switch focus from the page to DevTools, some overlay elements automatically hide if they are triggered by focus. For example, drop-down lists, menus, or date pickers. The check_box Emulate a focused page option lets you debug such an element as if it is in focus.

Try emulating a focused page on this demo page:

1. Focus the input element. Another element appears under it.
2. Open DevTools. The DevTools window is now in focus instead of the page, so the element disappears again.
3. In Elements > Styles, click :hov, check check_box Emulate a focused page, and make sure the input element is selected. You can now inspect the element under it.

You can also find the same option on the Rendering panel.

To discover more ways to freeze an element, see Freeze screen and inspect disappearing elements.

To toggle a pseudo-class:

1. Select an element.
2. On the Elements panel, go to the Styles tab.
3. Click :hov.
4. Check the pseudo-class that you want to turn on.

In this example, you can see that DevTools applies the background-color declaration to the element, even though the element is not actually hovered over.

The Styles tab shows the following pseudo-classes for all elements:

• :active
• :focus
• :focus-within
• :target
• :hover
• focus-visible

Additionally, some elements may have their own pseudo-classes. When you select such an element, the Styles tab shows a Force specific element state section that you can expand and turn on pseudo-classes specific to the element.

See Add a pseudostate to a class for an interactive tutorial.

Pseudo-elements let you style specific parts of elements. Highlight pseudo-elements are document portions with a "selected" status and they are styled as "highlighted" to indicate this status to the user. For example, such pseudo-elements are ::selection, ::spelling-error, ::grammar-error, and ::highlight.

As mentioned in the specification, when multiple styles conflict, cascade determines the winning style.

To better understand the inheritance and priority of the rules, you can view the inherited highlight pseudo-elements:

1. Inspect the text below.

   I inherited the style of my parent's highlight pseudo-element. Select me!

2. Select a portion of the text above.

3. In the Styles tab, scroll down to find the Inherited from ::selection pseudo of... section.

Cascade layers enable more explicit control of your CSS files to prevent style-specificity conflicts. This is useful for large codebases, design systems, and when managing third-party styles in applications.

To view cascade layers, inspect the next element and open Elements > Styles.

In the Styles tab, view the 3 cascade layers and their styles: page, component and base.

To view the layer order, click the layer name or the Toggle CSS layers view button.

The page layer has the highest specificity, therefore the element's background is green.

To view a page in print mode:

1. Open the Command Menu.
2. Start typing Rendering and select Show Rendering.
3. For the Emulate CSS Media drop-down, select print.

The Coverage tab shows you what CSS a page actually uses.

1. Press Command+Shift+P (Mac) or Control+Shift+P (Windows, Linux, ChromeOS) while DevTools is in focus to open the Command Menu.

2. Start typing coverage.

3. Select Show Coverage. The Coverage tab appears.

4. Click Reload. The page reloads and the Coverage tab provides an overview of how much CSS (and JavaScript) is used from each file that the browser loads.

   Green represents used CSS. Red represents unused CSS.

5. Click a CSS file to see a line-by-line breakdown of what CSS it uses in the preview above.

   On the screenshot, lines 55 to 57 and 65 to 67 of devsite-google-blue.css are unused, whereas lines 59 to 63 are used.

See Force DevTools Into Print Preview Mode.

From a single drop-down menu in the Styles tab, you can copy separate CSS rules, declarations, properties, values

Additionally, you can copy CSS properties in JavaScript syntax. This option is handy if you're using CSS-in-JS libraries.

To copy CSS:

1. Select an element.
2. In the Elements > Styles tab, right-click a CSS property.

3. Select one of the following options from the drop-down menu:

   • Copy declaration. Copies the property and its value in CSS syntax: css property: value;
   • Copy property. Copies only the property name.
   • Copy value. Copies only the value.
   • Copy rule. Copies the entire CSS rule: css selector[, selector] { property: value; property: value; ... }
   • Copy declaration as JS. Copies the property and its value in JavaScript syntax: js propertyInCamelCase: 'value'
   • Copy all declarations. Copies all properties and their values in the CSS rule: css property: value; property: value; ...

   • Copy all declarations as JS. Copies all properties and their values in JavaScript syntax: ```js propertyInCamelCase: 'value', propertyInCamelCase: 'value', ...

   • Copy all CSS changes. Copies the changes you make in the Styles tab across all declarations.

   • View computed value. Takes you to the Computed tab.

This section lists all the ways you can change CSS in Elements > Styles.

Additionally, you can:

• Override CSS across page loads.
• Save modified CSS to your local sources in a workspace.

Since the order of declarations affects how an element is styled, you can add declarations in different ways:

• Add a inline declaration. Equivalent to adding a style attribute to the element's HTML.
• Add a declaration to a style rule.

What workflow should you use? For most scenarios, you probably want to use the inline declaration workflow. Inline declarations have higher specificity than external ones, so the inline workflow ensures that the changes take effect in the element as you'd expect. See Selector Types for more on specificity.

If you're debugging an element's styles and you need to specifically test what happens when a declaration is defined in different places, use the other workflow.

To add an inline declaration:

1. Select an element.
2. In the Styles tab, click between the brackets of the element.style section. The cursor focuses, allowing you to enter text.
3. Enter a property name and press Enter.

4. Enter a valid value for that property and press Enter. In the DOM Tree, you can see that a style attribute has been added to the element.

   On the screenshot, the margin-top and background-color properties have been applied to the selected element. In the DOM Tree you can see the declarations reflected in the element's style attribute.

To add a declaration to an existing style rule:

1. Select an element.
2. In the Styles tab, click between the brackets of the style rule to which you want to add the declaration. The cursor focuses, allowing you to enter text.
3. Enter a property name and press Enter.
4. Enter a valid value for that property and press Enter.

On the screenshot, a style rule gets the new border-bottom-style:groove declaration.

Double-click a declaration's name or value to change it. See Change enumerable values with keyboard shortcuts for shortcuts for quickly incrementing or decrementing a value by 0.1, 1, 10, or 100 units.

While editing an enumerable value of a declaration, for example, font-size, you can use the following keyboard shortcuts to increment the value by a fixed amount:

• Option+Up (Mac) or Alt+Up (Windows, Linux) to increment by 0.1.
• Up to change the value by 1, or by 0.1 if the current value is between -1 and 1.
• Shift+Up to increment by 10.
• Shift+Command+Up (Mac) or Control+Shift+Page Up (Windows, Linux) to increment the value by 100.

Decrementing also works. Just replace each instance of Up mentioned earlier with Down.

You can use your pointer to change any property with length, such as width, height, padding, margin, or border.

To change the length unit:

1. Hover over the unit name and notice that it's underlined.

2. Click the unit name to select a unit from the drop-down.

To change the length value:

1. Hover over the unit value and notice that your pointer changes to a horizontal double-headed arrow.

2. Drag horizontally to increase or decrease the value.

To adjust the value by 10, hold Shift when dragging.

To add a class to an element:

1. Select the element in the DOM Tree.
2. Click .cls.
3. Enter the name of the class in the Add New Class box.
4. Press Enter.

To toggle automatic dark mode or emulate the user's preference of light or dark themes:

1. On the Elements > Styles tab, click Toggle common rendering emulations.

2. Select one of the following from the drop-down list:

   • prefers-color-scheme: light. Indicates that the user prefers the light theme.
   • prefers-color-scheme: dark. Indicates that the user prefers the dark theme.
   • Automatic dark mode. Displays your page in dark mode even if you didn't implement it. Additionally, sets prefers-color-scheme to dark automatically.

This drop-down is a shortcut for Emulate CSS media feature prefers-color-scheme and Enable automatic dark mode options of the Rendering tab.

To enable or disable a class on an element:

1. Select the element in the DOM Tree.
2. Open the Element Classes section. See Add a class to an element. Below the Add New Class box are all of the classes that are being applied to this element.
3. Toggle the checkbox next to the class that you want to enable or disable.

To add a new style rule:

1. Select an element.
2. Click New Style Rule . DevTools inserts a new rule beneath the element.style rule.

On the screenshot, DevTools adds the h1.devsite-page-title style rule after clicking New Style Rule.

When adding a new style rule, click and hold New Style Rule to choose which style sheet to add the style rule to.

To toggle a single declaration on or off:

1. Select an element.
2. In the Styles tab, hover over the rule that defines the declaration. Checkboxes appear next to each declaration.
3. Check or clear the checkbox next to the declaration. When you clear a declaration, DevTools crosses it out to indicate that it's no longer active.

On the screenshot, the color property for the currently-selected element is toggled off.

See the corresponding section in Animations.

For more information, see Smooth and simple transitions with the View Transitions API.

See the corresponding section in Inspect CSS grid.

See Inspect and debug HD and non-HD colors with the Color Picker.

The Angle Clock provides a GUI for changing <angle>s in CSS property values.

To open the Angle Clock:

1. Select an element with angle declaration.

2. In the Styles tab, find the transform or background declaration that you want to change. Click the Angle Preview box next to the angle value.

   The small clocks to the left of -5deg and 0.25turn are the angle previews.

3. Click the preview to open the Angle Clock.

4. Change the angle value by clicking on the Angle Clock circle or scroll your mouse to increase / decrease the angle value by 1.

5. There are more keyboard shortcuts to change the angle value. Find out more in the Styles pane keyboard shortcuts.

The Shadow Editor provides a GUI for changing text-shadow and box-shadow CSS declarations.

To change shadows with the Shadow Editor:

1. Select an element with a shadow declaration. For example, select the next element.

2. In the Styles tab, find a shadow icon next to the text-shadow or box-shadow declaration.

3. Click the shadow icon to open the Shadow editor.

4. Change the shadow properties:

   • Type (only for box-shadow). Pick Outset or Inset.
   • X and Y offsets. Drag the blue dot or specify values.
   • Blur. Drag the slider or specify a value.
   • Spread (only for box-shadow). Drag the slider or specify a value.

5. Observe the changes applied to the element.

The Easing Editor provides a GUI for changing the values of transition-timing-function and animation-timing-function.

To open the Easing Editor:

1. Select an element with a timing function declaration, like the <body> element on this page.
2. In the Styles tab, find the purple icon next to the transition-timing-function, animation-timing-function declarations, or the transition shorthand property.
3. Click the icon to open the Easing Editor:

To adjust timings with a click, use the presets in the Easing Editor:

1. In the Easing Editor, to set a keyword value, click one of the picker buttons:

2. In the Presets switcher, click or buttons to pick one of the following presets:

   • Linear presets: elastic, bounce, or emphasized.
   • Cubic Bezier presets:

To set custom values for timing functions, use the control points on the lines:

• For linear functions, click anywhere on the line to add a control point and drag it. Double-click to remove the point.

• For Cubic Bezier functions, drag one of the control points.

Any change triggers a ball animation in the Preview at the top of editor.

With this experiment enabled, the Styles tab highlights your CSS changes in green.

To copy a single CSS declaration change, hover over the highlighted declaration and click the Copy button.

To copy all CSS changes across declarations at once, right-click on any declaration and select Copy all CSS changes.

Additionally, you can track changes you make with the Changes tab.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4