Closed Bug 504082 Opened 11 years ago Closed 10 years ago
Don't let add-on developers list the add-on's page as the home or support page
Ok, this is just annoying. The extension at: https://addons.mozilla.org/en-US/firefox/addon/3977 lists its homepage URL as: https://addons.mozilla.org/en-US/firefox/addon/3977 and its support URL as: https://addons.mozilla.org/en-US/firefox/addon/3977 Um, can someone please at some point add a check for homepage or support URLs that are or redirect to the AMO page? This is dumb. :)
I tend to agree!
It's probably best to just disallow anything on the addons.mozilla.org domain.
I'll add this task bug to http://docs.google.com/Doc?id=dcfr9qrp_1c2pgcsfh (Bug 371210) While this is not quite a security vulnerability, it is related to upload checks.
Well, this isn't a problem with the add-on itself so it's not a check you can do on upload. I don't see any problem with listing the homepage in the install.rdf as the AMO page, in fact I do it for one of my extensions. This only really pertains to the fields you can set for the public page via the developer tools.
(In reply to comment #4) > Well, this isn't a problem with the add-on itself so it's not a check you can > do on upload. I don't see any problem with listing the homepage in the > install.rdf as the AMO page, in fact I do it for one of my extensions. This > only really pertains to the fields you can set for the public page via the > developer tools. Right, I mixed up the two, sorry.
Listing the add-on details page as the add-on homepage is different from listing it as the support website. As for the add-on homepage: I feel bad if we just disallow developers listing pages in the addons.mozilla.org domain as the add-on homepage without giving them a clear explanation. Before doing that, can you consider adding some explanation to the form in the Developer Tools along the line: “This address will be shown on the public page of your add-on. You can leave it blank if the add-on does not have a homepage other than the page on addons.mozilla.org.” Although the current explanation says “If your add-on has another homepage” (note the word “another”), it can be overlooked too easily. As for the support website: Assuming that reviews are not the right place to ask for support, I doubt that putting the add-on details page as the support webpage does any good. Therefore, I do not feel bad about disallowing it.
Severity: normal → trivial
Priority: -- → P3
Target Milestone: --- → 5.5
Now that we have the ability to incorporate getsatisfaction onto add-on pages, it's possible someone would use their add-on page as their support page. A link to getsatisfaction would be better, but they may have explanations or something in their description that could help people. I think this is a wontfix.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.