10

When editing a question on Cryptography.SE I noticed that when using the full (adress-bar) link, the full (raw) link would also appear in the preview and when saved it would properly show the title.

Example (open in edit mode to see the raw link):

Observed behavior:

Illustration

Expected behavior:

2nd Illustration

To clarify:

  • The bug occurs for both HTTP and HTTPS links
  • The bug occurs also (or especially?) for Same-Site-Links (ie MSE -> MSE or Crypto -> Crypto)
  • I do use HTTPS Everywhere and Firefox on Windows (10), which seems to break stuff here on SE sometimes
Improve this question
11
  • Specifically, URLs with the https scheme. Guess it's another item to add to the transition list, heh
    – Tim Stone
    Commented Mar 7, 2017 at 15:53
  • @TimStone actually, the original point where I discovered this was with http URLs. And indeed this bug also applies to http URLs (I just verified that)
    – SEJPM
    Commented Mar 7, 2017 at 15:54
  • @TimStone no, that's the first thing I checked when trying to reproduce. Any link isn't parsed, not only https links
    – Shadow Wizard
    Commented Mar 7, 2017 at 15:56
  • @ShadowWizard Switching it to http here seems to work fine for me though?
    – Tim Stone
    Commented Mar 7, 2017 at 15:56
  • @TimStone are you talking about the protocol used to navigate MSE (I always use HTTPS there) or about the protocol embedded in the link?
    – SEJPM
    Commented Mar 7, 2017 at 15:57
  • @TimStone not here, it happens when you try to link to a question on different site, e.g. to this question on Cryptography.SE as OP did, or from any other non MSE site.
    – Shadow Wizard
    Commented Mar 7, 2017 at 15:57
  • @ShadowWizard In a way inconsistent with the 2a not applying in preview restriction, or?
    – Tim Stone
    Commented Mar 7, 2017 at 16:08
  • @SEJPM The protocol in the link; the only example I see in your edit history is a http -> https swap (and the http variant works for me), but maybe that's not the one you're referring to
    – Tim Stone
    Commented Mar 7, 2017 at 16:09
  • @Tim oh, so it never worked? Might be, not 100% sure about that. If so you can write answer here quoting the restrictions, saying that links from main sites to other main sites are not parsed.
    – Shadow Wizard
    Commented Mar 7, 2017 at 16:15
  • OK, so the issues I demonstrated here and on crypto are links to other questions on the same site (ie crypto -> crypto and MSE -> MSE). They do appear for me regardless of whether the link uses http or https. It may have something to do with the fact that I use HTTPS Everywhere (which seems to break subtle details more often than not on SE it appears). The original crypto reference Q is this one. My edits on this Q was a HTTP -> HTTPS conversion (I encountered the bug pre- and post-edit) and here a HTTPS -> HTTP -> HTTPS test.
    – SEJPM
    Commented Mar 7, 2017 at 16:19
  • 1
    Ohhh, yeah, I see now @SEJPM. The API request is still using JSONP (whyyyyy?) and does so over HTTP exclusively, so the insecure request is blocked when you're browsing the site via HTTPS. Several simultaneous bugs here!
    – Tim Stone
    Commented Mar 7, 2017 at 16:21

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .