Intent to Experiment: Document Subtitle (Fix PWA app titles)
Diego Gonzalez
Contact emails
Explainer
Specification
Design docs
Summary
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
Risks
Interoperability and Compatibility
There are no interoperability and compatibility risks.
Gecko: Defer (https://github.com/mozilla/standards-positions/issues/749)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/138)
Web developers: Positive
Other signals:
Security
https://docs.google.com/document/d/1CwYQEf98fI5z96Y6AsQdSafp70SD5STgepD5Z8cx1HQ/edit
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
Debuggability
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
|
123
|
Link to entry on the Chrome Platform Status
Links to previous Intent discussions
Manuel Rego Casasnovas
On 20/02/2024 18:47, 'Diego Gonzalez' via blink-dev wrote:
> Specification
>
> https://github.com/whatwg/html/compare/main...diekus:html:main
Should this be an actual HTML PR so discussion with third parties can
happen there?
> /Gecko/: Defer
> (https://github.com/mozilla/standards-positions/issues/749
> <https://github.com/mozilla/standards-positions/issues/749>)
>
> /WebKit/: No signal
> (https://github.com/WebKit/standards-positions/issues/138
> <https://github.com/WebKit/standards-positions/issues/138>)
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
Cheers,
Rego
Diego Gonzalez
Mike Taylor
Hey Diego,
Can you clarify what milestones you're requesting for the OT?
thx,
Mike
--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/217e2f71-9e9b-42a4-9fe4-afb538bd765bn%40chromium.org.
Diego Gonzalez
Mike Taylor
Cool - LGTM to experiment from M124 to M127 inclusive (I think that's what you requested - feel free to correct me if not).
later,
Mike
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c184833d-7367-4ad2-9470-d7d5e8e19a8dn%40chromium.org.