Editor Guide should mention handling of special links, e.g. The about: Protocol; information about Firefox | Edit Article | MDN

RESOLVED FIXED

Status

Developer Documentation
MDN Meta Docs
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: anaran, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

3 years ago
See these links:

https://developer.mozilla.org/en-US/docs/MDN/Contribute/Editor
https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Style_guide

  referenced from

https://developer.mozilla.org/en-US/docs/about%3A_protocol$edit

Details:

Editing this page shows href values to about: and chrome: are present.

E.g.
   <td><code><a href="about:about">about:about</a></code></td>

Viewing or previewing the page shows these href values are removed.

I can only guess this is for security reasons.

The links editor help documents behind

Editor Guide • Style Guide

(links provided above) only mention external links to Bugzilla and WebKit.

They should also document the link-removing behavior described here.

I would expect that about: and chrome: links would be preserved so that "Copy Link" would be possible via context menu if users want to visit them in a newly opened tab.

It's especially confusing marking them up as link that "do not work".

http://mzl.la/1vxCDgA
(Reporter)

Updated

3 years ago
Component: MDN Meta Docs → Editing
Product: Developer Documentation → Mozilla Developer Network
(Reporter)

Comment 1

3 years ago
Typo correction:

> The links editor help documents behind

The editor links to help documents behind

> 
> Editor Guide • Style Guide
> 
> (links provided above) only mention external links to Bugzilla and WebKit.
Component: Editing → MDN Meta Docs
Product: Mozilla Developer Network → Developer Documentation
I've updated docs to explain that about: and chrome: URLs are not allowed, and additionally cleaned up and improved the content on links in our contributor guide. That should essentially resolve this issue.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.