5 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5revision 5 of How to read Firefox "about:memory" correctly?How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Possible Duplicate:
Links with URIs of schemes other than http/https are brokenLinks with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

3 Migration of MSO links to MSE links
source | link

Possible Duplicate:
Links with URIs of schemes other than http/https are brokenLinks with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

Possible Duplicate:
Links with URIs of schemes other than http/https are broken

On revision 5 of How to read Firefox "about:memory" correctly? I tried to set markdown links to about:memory (a special "URL" similar to about:config supported by Mozilla based browsers), ad it didn't work...

  • When I tried the naive thing (using the link button and pasting about:memory), the editor set the link to http://about:memory which obviously didn't work.
  • When I edited the "target" portion of the link syntax to be about:memory it was not rendered as a link.
  • Even trying <a href="about:memory">about:memory</a> does not seem to work in the live preview. I didn't submit that edit because there didn't seem to be a reason to further pollute the edit history.

::sigh::

Admittedly it is a rare use case, but should our markdown support a broad selection of "protocols"? If not, should pure html support it?

2 insert duplicate link
source | link
    Post Closed as "exact duplicate" by dmckee, Rick Sladkey, Tim Stone, Jeff Atwood of
1
source | link