Intent to Experiment: Document Subtitle (Fix PWA app titles)

Skip to first unread message

Diego Gonzalez

Feb 20, 2024, 12:48:00 PMFeb 20

Contact emails



Design docs


Installed web apps can change the text on the title bar based on the page's content. The current behavior is that the installed web application will put the app's name from the manifest and append the page’s inner text from the `<title>` HTML tag in the head of the page. This often can create awkward titles for some web apps. This feature allows to specify complementary information about the current window of an installed running PWA. It adds a subtitle to the page to provide contextual information that is displayed in the window's title bar. This replaces the text contained in the HTML's title tag.

Blink component

TAG review

TAG review status



Interoperability and Compatibility

There are no interoperability and compatibility risks.

Gecko: Defer (

WebKit: No signal (

Web developers: Positive

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Goals for experimentation

Ongoing technical constraints


The DOM inspection in DevTools is sufficient.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?


This is a feature that works on desktop scenarios (Windows, Linux, MacOS), mobile platforms don't make use of it.

Is this feature fully tested by web-platform-tests?


DevTrial instructions

Flag name on chrome://flags


Finch feature name

Non-finch justification


Requires code in //chrome?


Tracking bug

Estimated milestones

DevTrial on desktop

Link to entry on the Chrome Platform Status

Links to previous Intent discussions

This intent message was generated by Chrome Platform Status.

Diego González
Senior Product Manager
Microsoft Edge

Manuel Rego Casasnovas

Feb 21, 2024, 3:47:46 AMFeb 21

On 20/02/2024 18:47, 'Diego Gonzalez' via blink-dev wrote:
> Specification
> <>

Should this be an actual HTML PR so discussion with third parties can
happen there?

> /Gecko/: Defer
> (
> <>)
> /WebKit/: No signal
> (
> <>)

This is closed as "oppose".

Anyway it seems these standard positions requests are quite old and for
a different initial proposal that has evolved and changed. Shouldn't we
reopen them (or fill new ones, I'm not sure about the best practice in
this case) and update them with the new proposal.

> Goals for experimentation

I think you should describe the goals of this intent-to-experiment.

> Estimated milestones
> DevTrial on desktop
> 123

And you should define the OriginTrial first and last milestones.


Diego Gonzalez

Feb 21, 2024, 11:16:31 AMFeb 21
to blink-dev, Manuel Rego
Hola Manuel,

Thanks for the heads up. In order for this to be an HTML PR, it requires interest from another vendor. I'll submit the updated explainer for cross-vendor position requests and follow-up on their new positions which may mean I could present an HTML PR instead of a chromium-only implementation. 


Mike Taylor

Mar 6, 2024, 11:38:48 AMMar 6
to Diego Gonzalez, blink-dev, Manuel Rego

Hey Diego,

Can you clarify what milestones you're requesting for the OT?


You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Diego Gonzalez

Mar 11, 2024, 3:47:35 PMMar 11
to blink-dev,, Manuel Rego, Diego Gonzalez
Hola Mike,

We're looking art M124 for 4 milestones.



Mike Taylor

Mar 11, 2024, 3:59:28 PMMar 11
to Diego Gonzalez, blink-dev, Manuel Rego

Cool - LGTM to experiment from M124 to M127 inclusive (I think that's what you requested - feel free to correct me if not).


Reply all
Reply to author
0 new messages