Skip to content
This repository has been archived by the owner on Mar 26, 2019. It is now read-only.

Commit

Permalink
Merge pull request #111 from OfficeDev/betrue-final-final-progressDraft1
Browse files Browse the repository at this point in the history
Update ProgressIndicator.md
  • Loading branch information
wdo3650 authored Sep 15, 2016
2 parents 89e03a6 + 9a5d569 commit 1b8b319
Showing 1 changed file with 26 additions and 1 deletion.
27 changes: 26 additions & 1 deletion src/documentation/pages/ProgressIndicator/ProgressIndicator.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,23 @@
# Progress Indicator
Displays the progress of an operation when the percentage complete can be determined. Unable to determine how much of the operation is complete? Use a Spinner instead.
Progress Indicators are used to show the completion status of an operation lasting more than 2 seconds. If the state of progress cannot be determined, use a Spinner instead. Progress Indicators can appear in a new panel, a flyout, under the UI initiating the operation, or even replacing the initiating UI, as long as the UI can return if the operation is canceled or is stopped.

Progress Indicators feature a bar showing total units to completion, and total units finished. The description of the operation appears above the bar, and the status in text appears below. The description should tell someone exactly what the operation is doing. Examples of formatting include:

**[Object]** is being **[operation name]**, or<br/>
**[Object]** is being **[operation name]** to **[destination name]** or<br/>
**[Object]** is being **[operation name]** from **[source name]** to **[destination name]**

Status text is generally in units elapsed and total units. If the operation can be canceled, an “X” glyph is used and should be placed in the upper right, aligned with the baseline of the operation name. When an error occurs, replace the status text with the error description using ms-fontColor-redDark.

Real-world examples include copying files to a storage location, saving edits to a file, and more. Use units that are informative and relevant to give the best idea to users of how long the operation will take to complete. Avoid time units as they are rarely accurate enough to be trustworthy. Also combine steps of a complex operation into one total bar to avoid “rewinding” the bar. Instead change the operation description to reflect the change if necessary. Bars moving backwards reduce confidence in the service.

## Best Practices
| Do |Don't |
| :------------- | :------------- |
| Use a Progress indicator when the total units to completion is known | Use a Progress indicator when the total units to completion is indeterminate |
| Display operation description | Use only a single word description |
| Show text above and/or below the bar | Show text to the right or left of the bar |
| Combine steps of a single operation into one bar | Cause progress to “rewind” to show new steps |

## Variants

Expand All @@ -11,6 +29,10 @@ Displays the progress of an operation when the percentage complete can be determ
![ProgressIndicator example](https://raw.githubusercontent.com/OfficeDev/office-ui-fabric-js/master/ghdocs/component_images/ProgressIndicator-default.png)
i--->

## States
Active<br/>
Error

## Using this component
1. Confirm that you have references to Fabric's CSS and JavaScript on your page:
```
Expand Down Expand Up @@ -41,6 +63,9 @@ i--->
## Dependencies
This component has no dependency on other components.

## Accessibility
Focus styles are included for all of the actions included within a Progress Indicator.

<!---
{{> ProgressIndicatorExampleJS }}
--->

0 comments on commit 1b8b319

Please sign in to comment.