1541869 - Geolocation permission prompt is displayed when the permission is blocked for the site

Status: RESOLVED DUPLICATE of bug 1330559

(Firefox :: Site Identity, defect, P2)

Description

[Alin Ilea, Desktop Test Engineering]

[Affected versions]
68.0a1 (2019-04-04)
67.0b7
66.0.2

[Affected platforms]
Windows 7/10 x64
Ubuntu 18.04
Mac OS 10.13

[Steps to reproduce]

1. Go to https://maps.yahoo.com/
2. Click on the map
3. Click on current location(bottom left)/Allow access - your location is shown
4. Go to "i" button -in the left to URL- to access site information panel
5. Press ">"(show connection details) --> More information
6. Go to permissions --> access your location, uncheck Use Default and select Block
7. Refresh the page, click on the map and press current location

[Expected result]
The permission doorhanger for location access should not appear,because the permission was changed from "always ask" to "block".

[Actual result]
The permission doorhanger is displayed once again even if the permission for geolocation was blocked for this site. This is also reflected in the site information panel.

[Regression-Range] Will try to find it asap.

[Note]
This is also reproducible on https://goo.gl/oosgTZ
Please note that on google maps the user is notified about the blocked geolocation permission

Comment 1

[Timea Cernea [:tbabos][inactive]]

Seems to be an old regression.

Pushlog:
13:06.06 INFO: Got as far as we can go bisecting nightlies...
13:06.06 INFO: Last good revision: d0830980ffdb36a10855d02a588b4869cad6707e (2016-09-03)
13:06.06 INFO: First bad revision: 401ea746b1a9d515032b66d1368510d09e4e5a8e (2016-09-04)

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d0830980ffdb36a10855d02a588b4869cad6707e&tochange=401ea746b1a9d515032b66d1368510d09e4e5a8e

Mozregression couldn't bisect further using taskcluster builds..

Comment 2

[Johann Hofmann [:johannh]]

Oh, wow, that's... weird. We should fix this.

Comment 3

[Johann Hofmann [:johannh]]

This is caused by the sites embedding iframes for asking for geolocation, so it is just a duplicate of bug 1330559, which will be solved once we ship Feature Policy (see bug 1531012). It's a really bad situation. :(