Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit a57e562

Browse filesBrowse files
guardrexguardrex
authored
Change en dash layout elements to colon-space syntax (#18506)
* Change en dash layout elements to colon-space syntax * Update * Update
1 parent 40b4189 commit a57e562
Copy full SHA for a57e562

File tree

Expand file treeCollapse file tree

71 files changed

+381
-381
lines changed
Open diff view settings
Filter options

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Dismiss banner
Expand file treeCollapse file tree

71 files changed

+381
-381
lines changed
Open diff view settings
Collapse file

‎aspnetcore/blazor/call-javascript-from-dotnet.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/call-javascript-from-dotnet.md
+2-2Lines changed: 2 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -71,8 +71,8 @@ To use the <xref:Microsoft.JSInterop.IJSRuntime> abstraction, adopt any of the f
7171

7272
In the client-side sample app that accompanies this topic, two JavaScript functions are available to the app that interact with the DOM to receive user input and display a welcome message:
7373

74-
* `showPrompt` &ndash; Produces a prompt to accept user input (the user's name) and returns the name to the caller.
75-
* `displayWelcome` &ndash; Assigns a welcome message from the caller to a DOM object with an `id` of `welcome`.
74+
* `showPrompt`: Produces a prompt to accept user input (the user's name) and returns the name to the caller.
75+
* `displayWelcome`: Assigns a welcome message from the caller to a DOM object with an `id` of `welcome`.
7676

7777
*wwwroot/exampleJsInterop.js*:
7878

Collapse file

‎aspnetcore/blazor/call-web-api.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/call-web-api.md
+7-7Lines changed: 7 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,9 @@ The client's base address is set to the originating server's address. Inject an
5757

5858
In the following examples, a Todo web API processes create, read, update, and delete (CRUD) operations. The examples are based on a `TodoItem` class that stores the:
5959

60-
* ID (`Id`, `long`) &ndash; Unique ID of the item.
61-
* Name (`Name`, `string`) &ndash; Name of the item.
62-
* Status (`IsComplete`, `bool`) &ndash; Indication if the Todo item is finished.
60+
* ID (`Id`, `long`): Unique ID of the item.
61+
* Name (`Name`, `string`): Name of the item.
62+
* Status (`IsComplete`, `bool`): Indication if the Todo item is finished.
6363

6464
```csharp
6565
private class TodoItem
@@ -72,7 +72,7 @@ private class TodoItem
7272

7373
JSON helper methods send requests to a URI (a web API in the following examples) and process the response:
7474

75-
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsync%2A> &ndash; Sends an HTTP GET request and parses the JSON response body to create an object.
75+
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsync%2A>: Sends an HTTP GET request and parses the JSON response body to create an object.
7676

7777
In the following code, the `todoItems` are displayed by the component. The `GetTodoItems` method is triggered when the component is finished rendering ([OnInitializedAsync](xref:blazor/lifecycle#component-initialization-methods)). See the sample app for a complete example.
7878

@@ -88,7 +88,7 @@ JSON helper methods send requests to a URI (a web API in the following examples)
8888
}
8989
```
9090

91-
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PostAsJsonAsync%2A> &ndash; Sends an HTTP POST request, including JSON-encoded content, and parses the JSON response body to create an object.
91+
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PostAsJsonAsync%2A>: Sends an HTTP POST request, including JSON-encoded content, and parses the JSON response body to create an object.
9292

9393
In the following code, `newItemName` is provided by a bound element of the component. The `AddItem` method is triggered by selecting a `<button>` element. See the sample app for a complete example.
9494

@@ -116,7 +116,7 @@ JSON helper methods send requests to a URI (a web API in the following examples)
116116
var content = response.Content.ReadFromJsonAsync<WeatherForecast>();
117117
```
118118

119-
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PutAsJsonAsync%2A> &ndash; Sends an HTTP PUT request, including JSON-encoded content.
119+
* <xref:System.Net.Http.Json.HttpClientJsonExtensions.PutAsJsonAsync%2A>: Sends an HTTP PUT request, including JSON-encoded content.
120120

121121
In the following code, `editItem` values for `Name` and `IsCompleted` are provided by bound elements of the component. The item's `Id` is set when the item is selected in another part of the UI and `EditItem` is called. The `SaveItem` method is triggered by selecting the Save `<button>` element. See the sample app for a complete example.
122122

@@ -302,7 +302,7 @@ To allow other sites to make cross-origin resource sharing (CORS) requests to yo
302302

303303
## Additional resources
304304

305-
* <xref:security/blazor/webassembly/additional-scenarios> &ndash; Includes coverage on using <xref:System.Net.Http.HttpClient> to make secure web API requests.
305+
* <xref:security/blazor/webassembly/additional-scenarios>: Includes coverage on using <xref:System.Net.Http.HttpClient> to make secure web API requests.
306306
* <xref:fundamentals/http-requests>
307307
* <xref:security/enforcing-ssl>
308308
* [Kestrel HTTPS endpoint configuration](xref:fundamentals/servers/kestrel#endpoint-configuration)
Collapse file

‎aspnetcore/blazor/common/samples/3.x/BlazorServerSample/Shared/NavMenu.razor‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/common/samples/3.x/BlazorServerSample/Shared/NavMenu.razor
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@
3939
</li>
4040
<li class="nav-item px-3">
4141
<NavLink class="nav-link" href="CascadingValuesParametersTheme">
42-
<span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; Theme
42+
<span class="oi oi-plus" aria-hidden="true"></span> Cascading: Theme
4343
</NavLink>
4444
</li>
4545
<li class="nav-item px-3">
4646
<NavLink class="nav-link" href="CascadingValuesParametersTabSet">
47-
<span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; TabSet
47+
<span class="oi oi-plus" aria-hidden="true"></span> Cascading: TabSet
4848
</NavLink>
4949
</li>
5050
<li class="nav-item px-3">
Collapse file

‎aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Shared/NavMenu.razor‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/common/samples/3.x/BlazorWebAssemblySample/Shared/NavMenu.razor
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@
3939
</li>
4040
<li class="nav-item px-3">
4141
<NavLink class="nav-link" href="CascadingValuesParametersTheme">
42-
<span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; Theme
42+
<span class="oi oi-plus" aria-hidden="true"></span> Cascading: Theme
4343
</NavLink>
4444
</li>
4545
<li class="nav-item px-3">
4646
<NavLink class="nav-link" href="CascadingValuesParametersTabSet">
47-
<span class="oi oi-plus" aria-hidden="true"></span> Cascading &ndash; TabSet
47+
<span class="oi oi-plus" aria-hidden="true"></span> Cascading: TabSet
4848
</NavLink>
4949
</li>
5050
<li class="nav-item px-3">
Collapse file

‎aspnetcore/blazor/components.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/components.md
+3-3Lines changed: 3 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,8 @@ Razor components in Blazor apps extensively use Razor syntax. If you aren't fami
7070

7171
When accessing the content on Razor syntax, pay special attention to the following sections:
7272

73-
* [Directives](xref:mvc/views/razor#directives) &ndash; `@`-prefixed reserved keywords that typically change the way component markup is parsed or function.
74-
* [Directive attributes](xref:mvc/views/razor#directive-attributes) &ndash; `@`-prefixed reserved keywords that typically change the way component elements are parsed or function.
73+
* [Directives](xref:mvc/views/razor#directives): `@`-prefixed reserved keywords that typically change the way component markup is parsed or function.
74+
* [Directive attributes](xref:mvc/views/razor#directive-attributes): `@`-prefixed reserved keywords that typically change the way component elements are parsed or function.
7575

7676
## Static assets
7777

@@ -975,7 +975,7 @@ However, inline SVG markup isn't supported in all scenarios. If you place an `<s
975975

976976
## Additional resources
977977

978-
* <xref:security/blazor/server/threat-mitigation> &ndash; Includes guidance on building Blazor Server apps that must contend with resource exhaustion.
978+
* <xref:security/blazor/server/threat-mitigation>: Includes guidance on building Blazor Server apps that must contend with resource exhaustion.
979979

980980
<!--Reference links in article-->
981981
[1]: <xref:mvc/views/razor#code>
Collapse file

‎aspnetcore/blazor/dependency-injection.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/dependency-injection.md
+2-2Lines changed: 2 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -131,8 +131,8 @@ The DI system is based on the DI system in ASP.NET Core. For more information, s
131131

132132
After services are added to the service collection, inject the services into the components using the [\@inject](xref:mvc/views/razor#inject) Razor directive. [`@inject`](xref:mvc/views/razor#inject) has two parameters:
133133

134-
* Type &ndash; The type of the service to inject.
135-
* Property &ndash; The name of the property receiving the injected app service. The property doesn't require manual creation. The compiler creates the property.
134+
* Type: The type of the service to inject.
135+
* Property: The name of the property receiving the injected app service. The property doesn't require manual creation. The compiler creates the property.
136136

137137
For more information, see <xref:mvc/views/dependency-injection>.
138138

Collapse file

‎aspnetcore/blazor/event-handling.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/event-handling.md
+1-1Lines changed: 1 addition & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Supported <xref:System.EventArgs> are shown in the following table.
8484
For more information, see the following resources:
8585

8686
* [EventArgs classes in the ASP.NET Core reference source (dotnet/aspnetcore release/3.1 branch)](https://github.com/dotnet/aspnetcore/tree/release/3.1/src/Components/Web/src/Web).
87-
* [MDN web docs: GlobalEventHandlers](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers) &ndash; Includes information on which HTML elements support each DOM event.
87+
* [MDN web docs: GlobalEventHandlers](https://developer.mozilla.org/docs/Web/API/GlobalEventHandlers): Includes information on which HTML elements support each DOM event.
8888

8989
## Lambda expressions
9090

Collapse file

‎aspnetcore/blazor/hosting-models.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/hosting-models.md
+1-1Lines changed: 1 addition & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ A Blazor app is composed of reusable elements of UI called *components*. A compo
9696
* Turned into HTML text (during prerendering&dagger;).
9797
* Used to efficiently update the markup during regular rendering.
9898

99-
&dagger;*Prerendering* &ndash; The requested Razor component is compiled on the server into static HTML and sent to the client, where it's rendered to the user. After the connection is made between the client and the server, the component's static prerendered elements are replaced with interactive elements. Prerendering makes the app feel more responsive to the user.
99+
&dagger;*Prerendering*: The requested Razor component is compiled on the server into static HTML and sent to the client, where it's rendered to the user. After the connection is made between the client and the server, the component's static prerendered elements are replaced with interactive elements. Prerendering makes the app feel more responsive to the user.
100100

101101
A UI update in Blazor is triggered by:
102102

Collapse file

‎aspnetcore/blazor/integrate-components.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/integrate-components.md
+2-2Lines changed: 2 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ Razor components can be integrated into Razor Pages and MVC apps. When the page
1717

1818
After [preparing the app](#prepare-the-app), use the guidance in the following sections depending on the app's requirements:
1919

20-
* Routable components &ndash; For components that are directly routable from user requests. Follow this guidance when visitors should be able to make an HTTP request in their browser for a component with an [`@page`](xref:mvc/views/razor#page) directive.
20+
* Routable components: For components that are directly routable from user requests. Follow this guidance when visitors should be able to make an HTTP request in their browser for a component with an [`@page`](xref:mvc/views/razor#page) directive.
2121
* [Use routable components in a Razor Pages app](#use-routable-components-in-a-razor-pages-app)
2222
* [Use routable components in an MVC app](#use-routable-components-in-an-mvc-app)
23-
* [Render components from a page or view](#render-components-from-a-page-or-view) &ndash; For components that aren't directly routable from user requests. Follow this guidance when the app embeds components into existing pages and views with the [Component Tag Helper](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper).
23+
* [Render components from a page or view](#render-components-from-a-page-or-view): For components that aren't directly routable from user requests. Follow this guidance when the app embeds components into existing pages and views with the [Component Tag Helper](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper).
2424

2525
## Prepare the app
2626

Collapse file

‎aspnetcore/blazor/progressive-web-app.md‎

Copy file name to clipboardExpand all lines: aspnetcore/blazor/progressive-web-app.md
+2-2Lines changed: 2 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -113,14 +113,14 @@ The built-in *service-worker.published.js* service worker resolves requests usin
113113

114114
The cache-first strategy is valuable because:
115115

116-
* **It ensures reliability.** &ndash; Network access isn't a boolean state. A user isn't simply online or offline:
116+
* **It ensures reliability.** Network access isn't a boolean state. A user isn't simply online or offline:
117117

118118
* The user's device may assume it's online, but the network might be so slow as to be impractical to wait for.
119119
* The network might return invalid results for certain URLs, such as when there's a captive WIFI portal that's currently blocking or redirecting certain requests.
120120

121121
This is why the browser's `navigator.onLine` API isn't reliable and shouldn't be depended upon.
122122

123-
* **It ensures correctness.** &ndash; When building a cache of offline resources, the service worker uses content hashing to guarantee it has fetched a complete and self-consistent snapshot of resources at a single instant in time. This cache is then used as an atomic unit. There's no point asking the network for newer resources, since the only versions required are the ones already cached. Anything else risks inconsistency and incompatibility (for example, trying to use versions of .NET assemblies that weren't compiled together).
123+
* **It ensures correctness.** When building a cache of offline resources, the service worker uses content hashing to guarantee it has fetched a complete and self-consistent snapshot of resources at a single instant in time. This cache is then used as an atomic unit. There's no point asking the network for newer resources, since the only versions required are the ones already cached. Anything else risks inconsistency and incompatibility (for example, trying to use versions of .NET assemblies that weren't compiled together).
124124

125125
### Background updates
126126

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.