Debug CSS styles using DOM Explorer

Artikel
11/15/2016

Note

This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

Applies to Windows and Windows Phone](../Image/windows_and_phone_content.png "windows_and_phone_content")

When you're debugging Windows Store apps, Windows Phone Store apps, and apps created using Visual Studio Tools for Apache Cordova, you can view and change CSS rules for selected DOM elements and their child elements.

The Styles and Computed tabs in DOM Explorer show the CSS rules that apply to a selected element. The rules are displayed in the order of their specificity according to CSS precedence rules. Rules at the top of a selector or style in a tab (the most specific rules) are the last to be applied to the selected element, and rules at the bottom of a selector or style are the first to be applied. When rules are applied, they override previously applied rules.

The Styles, Computed, and Changes tabs provide different views of style information.

Use the Styles tab to view rules organized by CSS selector name, such as html, body. You can also use this tab to enable or disable specific styles, manually edit values, and to see the immediate results of these changes.
Use the Computed tab to view the computed values of a style. For example, if you set a size to 1em, the value computed by Internet Explorer might be 16px. Styles in this tab are organized by style name, such as height. You can also use this tab to enable or disable specific styles, manually edit values, and to see the immediate results of these changes.

Note

In Visual Studio 2013 Update 2, the information provided in the Trace tab has been merged with the Computed tab, and the Trace tab has been removed.
Use the Changes tab (Windows Store and Windows Phone Store apps only) to identify and track CSS styles that you have changed during a debugging session.

Tip

Changes you make to styles in the Styles and Computed tabs aren't permanent. They're lost when you stop debugging. To change source code and reload pages without stopping and restarting the debugger, refresh your app by using the Refresh Windows app button button (Refresh Windows app) on the Debug toolbar (Windows Store and Windows Phone Store apps only). For more info, see Refresh an app (JavaScript).

Example of fixing a CSS rule

This example shows how to inspect CSS rules and debug a style issue. For this example, let's say that you want to change the color of a font used to display group titles in the Windows 8.x Store Split App template.

Note

This example shows a Windows Store app, but all the DOM Explorer features shown also apply to a Windows Phone Store app and, except for the Changes tab, an app created using Visual Studio Tools for Apache Cordova.

To view and change CSS rules

In Visual Studio, create a Windows 8.x Store app using JavaScript and HTML in the Split App project template.
In Solution Explorer, open items.css. (You can find items.css in the pages folder.)

Replace the following CSS code:

.itemspage .itemslist .item {  
    -ms-grid-columns: 1fr;  
    -ms-grid-rows: 1fr 90px;  
    display: -ms-grid;  
    height: 250px;  
    width: 250px;  
}

with this:

.itemspage .itemslist .item {  
    -ms-grid-columns: 1fr;  
    -ms-grid-rows: 1fr 90px;  
    display: -ms-grid;  
    height: 250px;  
    width: 250px;  
    color: #ff6a00;  
}

This adds a style that specifies the color #ff6a00 (orange) for each item in the list. The CSS selector, .itemspage .itemslist .item, indicates a set of class names for DIV elements in items.html, which appear as nested elements in the live DOM. The item DIV element specifies the list items.

Select Simulator in the drop-down list on the Debug toolbar (Local Machine is the default value).
Press F5 to run your app in debug mode.

When the app finishes loading, look at the headings of the list items, such as Group Title: 1. The color is unchanged, so the attempt to apply an orange color to the titles didn't work. We'll figure out what went wrong and fix it by using the CSS tabs in DOM Explorer.

Tip

After the app appears in the Simulator, position the Simulator right next to the Visual Studio window so you can immediately see the results of your selections and changes you make to CSS styles.
Switch to Visual Studio and click Select Element in DOM Explorer (or press Ctrl+B). This changes the selection mode so that you can select an item by clicking it, and brings the app into the foreground. The mode reverts back after a single click. Here is the Select Element button.

Tip

You can also select HTML elements directly in DOM Explorer. For more info on selecting elements, see Quickstart: Debug HTML and CSS.
In the Simulator, hover over the title of the first item in the list, Group Title: 1, in the left panel of the home page. The title is highlighted, as shown here:

Note

The Windows Phone Emulator only partially supports highlighting elements by hovering.
Click the outlined title. DOM Explorer automatically selects the corresponding HTML element, which looks similar to this.
```
<h4 class="item-title">Group Title: 1</h4>  
```
When you select the H4 element in DOM Explorer, the DOM Explorer tabs now show the rules that are associated with the H4 element. The Computed tab is shown here, with the color property opened:

This view provides useful information about the rules that are associated with the color style, such as the following:
- The CSS selector we modified in items.css, .itemspage .itemslist .item, is not being used in the final style calculation (it appears in strikethrough text). Several other occurrences of the color style also aren't being used.
  
  Tip
  
  For longer selector names, the full name appears in a tooltip.
- The final computed CSS value, rgba(255, 255, 255, 0.87), is set specifically for the following CSS selector: .itemspage .itemslist .item .item-overlay .item-title, which is also defined in items.css.
  
  Tip
  
  Now that we know where the title color is set, we also know where we might change it. However, we can also test changes in DOM Explorer without refreshing the app, as shown in the remaining steps.
Clear the check box for the first occurrence of the color style, which is for the .itemspage .itemslist .item .item-overlay .item-title selector. Now, in the Simulator, you see that the color of the item titles all change to orange, as we intended, and the selector we modified in CSS, .itemspage .itemslist .item, is no longer overridden (that is, it no longer has strikethrough text applied). Here's the Computed tab after we clear the check box.
Select the Changes tab.

Use the Changes tab to identify and track style changes that you make during a debugging session . The following illustration shows the .itemspage .itemslist .item .item-overlay .item-title selector in the Changes tab, which is now overridden.
You can also manually edit CSS style values and see the immediate result by using the Styles tab.
Select the Styles tab.
Open the .itemspage .itemslist .item .item-overlay .item-title style selector.
Select the first occurrence of the color style, and then double-click the property value rgb(255, 255, 255, 0.87).
Use the keyboard to modify this value. Change it to rgb(255, 255, 0, 0.87), and then press Enter. The colors of the item titles in the Simulator all change to yellow.
To make changes to the source CSS file, click the items.css link on the Styles tab. This opens items.css, where you can change the value of the color style in your app code. To refresh the app without stopping and restarting the debugger, click the (Refresh Windows app) button on the Debug toolbar.

Freigeben über

Debug CSS styles using DOM Explorer

Example of fixing a CSS rule

To view and change CSS rules

See Also

Zusätzliche Ressourcen