remove syntax blocks

mdn · Sep 17, 2024 · 4efa5f0 · 4efa5f0
1 parent ad01be7
commit 4efa5f0
Show file tree

Hide file tree

Showing 15 changed files with 0 additions and 151 deletions.
diff --git a/files/en-us/web/manifest/background_color/index.md b/files/en-us/web/manifest/background_color/index.md
@@ -16,12 +16,6 @@ Therefore `background_color` should match the {{cssxref("background-color")}} CS
 > [!NOTE]
 > The `background_color` member is only meant to improve the user experience while the main stylesheet is loading from the network or the storage media; it is not used by the user agent as the {{cssxref("background-color")}} CSS property when the progressive web app stylesheet is available.
 
-## Syntax
-
-```json
-"background_color": "<color-value>"
-```
-
 ## Examples
 
 ```json

diff --git a/files/en-us/web/manifest/categories/index.md b/files/en-us/web/manifest/categories/index.md
@@ -15,12 +15,6 @@ There is no standard list of possible values, but the W3C maintains [a list of k
 
 > **Note:** `categories` values are lower-cased by the stores and catalogs before processing, so "News" and "news" are treated as the same value. Developers are encouraged to use lower case in the first place.
 
-## Syntax
-
-```json
-"categories": ["<category-name>", "<category-name>"]
-```
-
 ## Examples
 
 ```json

diff --git a/files/en-us/web/manifest/description/index.md b/files/en-us/web/manifest/description/index.md
@@ -7,15 +7,6 @@ browser-compat: html.manifest.description
 
 {{QuickLinksWithSubpages("/en-US/docs/Web/Manifest")}}
 
-<table class="properties">
-  <tbody>
-    <tr>
-      <th scope="row">Type</th>
-      <td><code>String</code></td>
-    </tr>
-  </tbody>
-</table>
-
 The `description` member is a string in which developers can explain what the application does. `description` is directionality-capable, which means it can be displayed left to right or right to left based on the values of the [`dir`](/en-US/docs/Web/Manifest) and [`lang`](/en-US/docs/Web/Manifest) manifest members.
 
 ## Examples

diff --git a/files/en-us/web/manifest/display_override/index.md b/files/en-us/web/manifest/display_override/index.md
@@ -13,12 +13,6 @@ The [`display`](/en-US/docs/Web/Manifest/display) member is used to determine th
 
 The `display_override` member solves this by letting the developer provide a sequence of display modes that the browser will consider before using the `display` member. Its value is an array of display modes that are considered in-order, and the first supported display mode is applied.
 
-## Syntax
-
-```json
-"display_override": ["<display-keyword>", "<display-keyword>"]
-```
-
 ### Values
 
 Display override objects are display-mode strings, the possible values are:

diff --git a/files/en-us/web/manifest/file_handlers/index.md b/files/en-us/web/manifest/file_handlers/index.md
@@ -18,20 +18,6 @@ For example, a PWA can be registered to handle files that match the `text/plain`
 > [!NOTE]
 > While the `file_handlers` member is used to register a PWA with a given set of file types, this only results in the operating system launching the PWA when a matching file is opened. The PWA then needs to actually handle the file using JavaScript code. See [Handling the files](#handling_the_files) for more information.
 
-## Syntax
-
-```json
-"file_handlers": [
-  {
-    "action": "<action-url>",
-    "accept": {
-      "<mime-type>": ["<file-Extension>", "<file-Extension>"],
-      "<mime-type>": ["<file-Extension>"]
-    }
-  }
-]
-```
-
 ### Values
 
 An array of objects. Each object in the array must contain the following values (`action` and `accept` are required):

diff --git a/files/en-us/web/manifest/id/index.md b/files/en-us/web/manifest/id/index.md
@@ -16,12 +16,6 @@ If the `id` is unspecified or invalid in any way (such as not a string, not a va
 > [!NOTE]
 > The `id` member can be used to uniquely identify applications. The `id` member is processed like a `start_url` but can be out of [scope](/en-US/docs/Web/Manifest/scope) because it does not point to a resource that can be navigated to.
 
-## Syntax
-
-```json
-"id": "<app-identifier>"
-```
-
 ## Examples
 
 ```json

diff --git a/files/en-us/web/manifest/launch_handler/index.md b/files/en-us/web/manifest/launch_handler/index.md
@@ -11,14 +11,6 @@ browser-compat: html.manifest.launch_handler
 
 The `launch_handler` member defines values that control the launch of a web application. Currently it can only contain a single value, `client_mode`, which specifies the context in which the app should be loaded when launched. For example, in an existing web app client containing an instance of the app, or in a new web app client. This leaves scope for more `launch_handler` values to be defined in the future.
 
-## Syntax
-
-```json
-"launch_handler": {
-  "client_mode": ["<context-keyword>", "<context-keyword>"]
-}
-```
-
 ### Values
 
 `launch_handler` objects may contain the following values:

diff --git a/files/en-us/web/manifest/name/index.md b/files/en-us/web/manifest/name/index.md
@@ -9,12 +9,6 @@ browser-compat: html.manifest.name
 
 The `name` member is a string that represents the name of the web application as it is usually displayed to the user (e.g., amongst a list of other applications, or as a label for an icon). `name` is directionality-capable, which means it can be displayed left-to-right or right-to-left based on the values of the [`dir`](/en-US/docs/Web/Manifest) and [`lang`](/en-US/docs/Web/Manifest) manifest members.
 
-## Syntax
-
-```json
-"name": "<app-name>"
-```
-
 ## Examples
 
 Simple `name` in left-to-right language:

diff --git a/files/en-us/web/manifest/orientation/index.md b/files/en-us/web/manifest/orientation/index.md
@@ -14,12 +14,6 @@ The `orientation` member defines the default orientation for all the website's t
 > [!NOTE]
 > The orientation can be changed at runtime via the [Screen Orientation API](/en-US/docs/Web/API/Screen_Orientation_API).
 
-## Syntax
-
-```json
-"orientation": "<orientation-keyword>"
-```
-
 ### Values
 
 `orientation` can take one of the following values:

diff --git a/files/en-us/web/manifest/protocol_handlers/index.md b/files/en-us/web/manifest/protocol_handlers/index.md
@@ -13,17 +13,6 @@ The `protocol_handlers` member specifies an array of objects that are protocols
 
 After registering a web app as a protocol handler, when a user clicks on a hyperlink with a specific scheme such as `mailto://` or `web+music://` from a browser or native app, the registered PWA would open and receive the URL.
 
-## Syntax
-
-```json
-"protocol_handlers": [
-  {
-    "protocol": "<protocol>",
-    "url": "<url>"
-  }
-  ]
-```
-
 ### Values
 
 Protocol handlers objects may contain the following values:

diff --git a/files/en-us/web/manifest/scope/index.md b/files/en-us/web/manifest/scope/index.md
@@ -13,12 +13,6 @@ A valid `scope` needs to allow [`start_url`](/en-US/docs/Web/Manifest/start_url)
 
 If `scope` is unspecified or invalid in any way (such as not a string, not a valid URL, or causes `start_url` to be out of scope), the `start_url` is used, with its last path segment removed.
 
-## Syntax
-
-```json
-"scope": "<scope-url>"
-```
-
 ## Examples
 
 If the scope is relative, the manifest URL is used as a base URL:

diff --git a/files/en-us/web/manifest/screenshots/index.md b/files/en-us/web/manifest/screenshots/index.md
@@ -11,21 +11,6 @@ browser-compat: html.manifest.screenshots
 
 The `screenshots` member defines an array of screenshots intended to showcase the application. These images are intended to be used by progressive web app stores.
 
-## Syntax
-
-```json
-"screenshots": [
-  {
-    "form_factor": "<device-keyword>",
-    "label": "<accessible-name>",
-    "platform": "<platform-keyword>",
-    "sizes": "<size-values>",
-    "src": "<image-url>",
-    "type": "<mime-type>"
-  }
-]
-```
-
 ### Values
 
 The `screenshots` member is an array of objects each representing a screenshot. Each screenshot object may contain the following properties:

diff --git a/files/en-us/web/manifest/serviceworker/index.md b/files/en-us/web/manifest/serviceworker/index.md
@@ -12,16 +12,6 @@ browser-compat: html.manifest.serviceworker
 
 The `serviceworker` member specifies a serviceworker that is Just-In-Time (JIT)-installed and registered to run a web-based payment app providing a payment mechanism for a specified payment method in a merchant website. See {{domxref("Payment Handler API", "Payment Handler API", "", "nocode")}} for more details.
 
-## Syntax
-
-```json
-"serviceworker": {
-  "scope": "<scope-path>",
-  "src": "<script-path>",
-  "use_cache": true
-}
-```
-
 ### Values
 
 `serviceworker` objects may contain the following values:

diff --git a/files/en-us/web/manifest/share_target/index.md b/files/en-us/web/manifest/share_target/index.md
@@ -16,27 +16,6 @@ Once registered and installed, a PWA that uses the Web Share Target API acts as
 > [!NOTE]
 > If you want to share data using the Web Share API, see [Web Share API](/en-US/docs/Web/API/Web_Share_API) and [`navigator.share()`](/en-US/docs/Web/API/Navigator/share).
 
-## Syntax
-
-```json
-"share_target": {
-  "action": "<target-url>",
-  "enctype": "<encoding-type>",
-  "method": "<http-method-keyword>",
-  "params": {
-    "title": "<title>",
-    "text": "<text>",
-    "url": "<url>",
-    "files": [
-      {
-        "name": "<file-name>",
-        "accept": ["<mime-type>", "<file-extension>"]
-      }
-    ]
-  }
-}
-```
-
 ### Values
 
 The value of the `share_target` member is an object that defines how an application can receive shared data. This object may contain the following properties (`action` and `params` are required):

diff --git a/files/en-us/web/manifest/shortcuts/index.md b/files/en-us/web/manifest/shortcuts/index.md
@@ -9,27 +9,6 @@ browser-compat: html.manifest.shortcuts
 
 The `shortcuts` member defines an array of shortcuts or links to key tasks or pages within a web app. A user agent can use these values to assemble a context menu to be displayed by the operating system when a user engages with the web app's icon. When user invokes a shortcut, the user agent will navigate to the address given by shortcut's `url` member.
 
-## Syntax
-
-```json
-"shortcuts": [
-  {
-    "name": "<app-name>",
-    "short_name": "<short-app-name>",
-    "description": "<description>",
-    "url": "<url>",
-    "icons": [
-      {
-        "src": "<icon-url>",
-        "sizes": "<size-values>",
-        "type": "<mime-type>",
-        "purpose": "<purpose-keyword>"
-      }
-    ]
-  }
-]
-```
-
 ### Values
 
 Shortcut objects may contain the following values (only `name` and `url` are required):