1644802 - Right click copy image location inconsistent

Status: RESOLVED DUPLICATE of bug 1719203

(Core :: DOM: Core & HTML, defect, P3)

Description

[Jeremy Selier]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

1. Open new tab
2. Load https://picsum.photos/
3. Right click > Copy image Location

Actual results:

URL being paste is the URL after redirects: https://i.picsum.photos/id/949/536/354.jpg instead of before redirects: https://picsum.photos/536/354

Refreshing the page and trying again shows https://picsum.photos/536/354

Expected results:

It should be https://picsum.photos/536/354 from the start all the time and never past the redirected URL (eg it should always return the URL in the SRC attribute).

Comment 1

[Alice0775 White]

Reression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=72ee4800d4156931c89b58bd807af4a3083702bb&tochange=0ee6ca490391aaba9f8e512b64b0a784b5dc226a

Regressed by: Bug 1406253

Comment 2

[Emilio Cobos Álvarez (:emilio)]

Hmm, why is the expected result that? Both behaviors seem somewhat reasonable.

Comment 3

[Alice0775 White]

1. Load https://picsum.photos/
2. Right click > Copy image Location
   --- observe, clipboard shows https://i.picsum.photos/id/949/536/354.jpg
3. Reload(F5)
4. Right click > Copy image Location
   --- observe, clipboard shows https://picsum.photos/536/354

It is inconsistent results between step 2 and step4. Why?

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Ah, I missed that... The inconsistent behavior does look a bit odd. I suspect it's related to the image being cached, but not being cacheable (which causes us to revalidate the load), vs. the first time on which we load the image completely.

Comment 5

[Jeremy Selier]

In terms of expected behavior I just said this because:

1. From my tests, all other browsers have this behavior
2. It seems from a developer standpoint, I'd prefer to expose the URL in src and not wherever it might redirect. It could redirect to a URL that expires etc. It seems better and more logical to me to always expose the URL that was specified by the developer.

Up to you obviously.

Comment 6

[John Dai[:jdai]]

Hi Edgar,
Could you please help to take a look? Thank you.

Comment 7

[Jeremy Selier]

Friendly ping, any chances this can be looked at?

Comment 8

[Edgar Chen [:edgar]]

I plan to take a look at, but have no time yet.
Per bug 1406253, it looks like using redirect URI in context menu is what we expect, and we should have consistent behavior on the image being cached.