Open Bug 1627264 Opened 10 months ago Updated 7 months ago

Allowing location in Outlook Calendar put two location icon in URL bar

Categories

(Firefox :: Site Permissions, defect, P3)

74 Branch
defect

Tracking

()

People

(Reporter: zstimi, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Attached image location-icon.png

Affected versions

  • Firefox 75.0
  • Firefox 74.0.1
  • Firefox 73.0.1
  • Firefox Nightly 76.0a1

Affected platforms

  • Windows 10 x64
  • Ubuntu 18.04 x64

Steps to reproduce

  1. Start Firefox.
  2. Go to https://outlook.live.com/calendar/view/month and login
  3. Click on any tile to create a new event and then click on "Add a location"
  4. Click on Allow Location Access from the popup

Expected result

  • The process of Allowing Location Access, and the tracking of the location is done without issues, in URL bar near lock icon appear one location icon.

Actual result

  • By selection on Allow Location Access in URL bar appear two location icon (see the attachment)

Regression range
I will come back with regression range ASAP.

Note

  • I don't think this is a recent regression, as it's reproducing on Fx 73.0.1.
  • On macOS platform this issue it is not reproducible.
Has Regression Range: --- → no
Has STR: --- → yes

Paul, did we have a bug tracking this? Is this by design? It might be better to only have one icon there, i.e. remove the "using geolocation" icon when the doorhanger is shown.

Component: Site Identity → Site Permissions
Flags: needinfo?(pbz)

I don't think we have a bug for this yet. Technically it's correct, but I can see how it could be confusing for users.
It happens when a user accepts geolocation access temporarily (checkbox unchecked) and the website makes another geolocation request.
Hiding the icon while the doorhanger is shown would work.

Flags: needinfo?(pbz)
Priority: -- → P3
Regressed by: 630614

This issue still occurs in the latest Nightly 77.0a1 (2020-04-13) on macOS 10.15. Will update the flags accordingly.

Paul, do you think this issue is a valid or an invalid bug?

Flags: needinfo?(pbz)

This is a valid bug (see my comment above). Not something we want to prioritize at the moment though.

Flags: needinfo?(pbz)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

Reproducible in the latest Nightly 78.0a1 (2020-05-27) as well. Updated the 78 flag accordingly.

Reproducible on latest Nightly version 79.0a1 (2020-06-24) on Ubuntu 20.04.

Reproducible on latest Nightly version 80.0a1 (2020-07-07) on Ubuntu 18.04. Flags are changed accordingly.

You need to log in before you can comment on or make changes to this bug.