-
Notifications
You must be signed in to change notification settings - Fork 82
Specify meaning of homepage_url and developer.url manifest keys #1006
Copy link
Copy link
Open
Labels
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timespec clarificationNeeds clarification when specifiedNeeds clarification when specified
Metadata
Metadata
Assignees
Labels
needs-triage: chromeChrome needs to assess this issue for the first timeChrome needs to assess this issue for the first timeneeds-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timeneeds-triage: safariSafari needs to assess this issue for the first timeSafari needs to assess this issue for the first timespec clarificationNeeds clarification when specifiedNeeds clarification when specified
Type
Fields
Give feedbackNo fields configured for issues without a type.
Background
Extensions can declare two types of URLs:
homepage_url(mdn) anddeveloper.url(mdn).Chromium-based browsers use
homepage_urlfor the "view extension website" feature in the extension configuration page.Opera is claimed to have support for
developer.urlyet I could not find any evidence for this. The claim is it would preferhomepage_urloverdeveloper.urlyet it seemsdeveloper.urlis simply never used.Firefox currently has a generic "Homepage" link in the extension configuration page and uses
developer.urlproperty withhomepage_urlas fallback. At the same time, it has a link next toauthorwhich links to the add-on store if it is an add-on store installed extension, else it is just text.Moving forward
Instead of deprecating one over the other, I believe we can redefine/clarify the properties meaning.
homepage_url: homepage of the individual extensiondeveloper.url: homepage of the author/publisher/developer in questionThis would mean Firefox probably needs to swap the above mentioned fallback logic if "homepage" is supposed to be about the extension homepage. For the author link,
developer.urlcan be used, unless for security/design reasons it should stay the add-on URL.Browsers currently not supporting
developer.urlcan introduce it as author/publisher/developer website link or use it as fallback for the website link in casehomepage_urlis missing.Note: this has partly been discussed in #67. To keep the issue clean and make sure status labels make sense, I split off the author part for additional clarity, with a clear goal: deprecate the
authorfield.