Closed
Bug 670047
Opened 13 years ago
Closed 13 years ago
Validator links file names to invalid URLs
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect, P4)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
WONTFIX
6.1.6
People
(Reporter: jorgev, Assigned: kumar)
References
()
Details
(Whiteboard: [ReviewTeam])
Attachments
(1 file)
86.08 KB,
image/png
|
Details |
Go to https://addons.mozilla.org/en-US/developers/addon/polychrome/file/124684/validation and look at the URLs where the files point to. For example: http://outgoing.mozilla.org/v1/f62e4efd99a629967262bd5b5a3063f0036905aa/http%3A//findpoly.sh
Comment 1•13 years ago
|
||
Kumar: Not sure if you added the linkifying code. Does this seem like it's related? Jorge: I'm not an admin on prod, so I get a 403. Any way you can find an example on allizom?
Assignee | ||
Comment 2•13 years ago
|
||
I think this is a bug in bleach.linkify(), I will verify. findpoly.sh is not a website, it is a file within the addon.
Assignee | ||
Comment 3•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Assignee: mbasta → kumar.mcmillan
Updated•13 years ago
|
Target Milestone: 6.1.5 → 6.1.6
Updated•13 years ago
|
Target Milestone: 6.1.6 → 6.1.8
Assignee | ||
Comment 4•13 years ago
|
||
Bleach issue for this: https://github.com/jsocol/bleach/issues/35
Target Milestone: 6.1.8 → 6.1.6
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #4) > Bleach issue for this: https://github.com/jsocol/bleach/issues/35 Given the state of that issue at the moment, and the fact that we do need to linkify the contents of the validator messages, I think this bug won't lead anywhere.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 6•13 years ago
|
||
Reclassifying editor bugs and changing to a new whiteboard flag. Spam, spam, spam, spam...
Whiteboard: [required amo-editors] → [ReviewTeam]
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•