You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DocumentSubtitle/explainer.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ To fix this situation, we require a bucket to store this contextual information.
34
34
## Use Cases
35
35
This will allow developers 2 cases for the standard title bar.
36
36
1. Installed web apps that only have the app’s name as define in the manifest file.
37
-
* Useful to replicate some native experiences that only have the app’s name in the title bar (This is the default behaviour for web apps that do not specify the app-title meta tag or define it through the JS API).
37
+
* Useful to replicate some native experiences that only have the app’s name in the title bar (This is the default behaviour for web apps that do not specify the app-title meta tag or set the content to a blank or empty string).
38
38
2. Installed Web Apps that have the app’s name and a app-title or detail as defined in the document’s meta tag.
39
39
* Useful for apps that can have multiple instances running with several documents open, such as word processors.
40
40
@@ -44,7 +44,6 @@ As defined in the [HTML specification](https://html.spec.whatwg.org/multipage/se
44
44
45
45
`<meta name="app-title" content="additional/secondary text to go in the title bar">`
46
46
47
-
48
47
The following image is a mockup of a PWA using the `app-title` meta-tag.
49
48
50
49

@@ -53,6 +52,8 @@ This is achieved by adding the following meta tag in the head of the page:
The TAG privacy and security self-review is located [here](https://docs.google.com/document/d/1CwYQEf98fI5z96Y6AsQdSafp70SD5STgepD5Z8cx1HQ/edit?usp=sharing).
0 commit comments