- From: Diego Gonzalez <notifications@github.com>
- Date: Wed, 24 Jan 2024 09:12:55 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/819/1908574461@github.com>
Hola! Update on this work. We have decided not to use any meta-data vocabularies (schema.org, opengraph) and instead focus on a new `name` value in the `meta` tag (`appTitle`). The solutions we explored seemed overengineered with a goal of representing any type of object (like persons, books, businesses) or with the intention of becoming a "rich object in a social graph". Both of those are not the scope of what we intend to do with fixing the text that can appear on the title of a web application. Ironically, these systems build on the same concept we are using, the meta tag. We've decided to add a new `name` value for the meta tag, which solves the issue at hand in a simple way that does not require a new API and allows to provide document-level meta data that applies to the whole page. This new name value is `appTitle`. If the meta tag with a `name="appTitle"` is not used (hence, there is no need to differentiate the text that appears on the tab on a browser with the text that appears on web content running in a standalone window) then there is no change whatsoever to how the webpage works, and if it is present then a developer can have control of the text that appears on the title bar of an app without having to alter the structure of the same content running on a tab. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/819#issuecomment-1908574461 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/819/1908574461@github.com>
Received on Wednesday, 24 January 2024 17:13:02 UTC