1543386 - Outlook Calendar not processing Geolocation info correctly

Status: NEW

(Developer Engagement :: Outreach Request, defect)

Description

[Catalin Sasca, Desktop QA [:csasca]]

Attachment: font.gif

Affected versions

• Firefox 66.0.3
• Firefox DevEdition 67.0b9
• Firefox Nightly 68.0a1

Affected platforms

• Windows 10 (x64)
• Windows 7 (x64)
• Ubuntu 18.04 (x64)
• macOS 10.12

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.

Actual result

• By selection on Allow Location Access, nothing happens (see the attachment)

Regression range

• I don't think this is a regression, as it is reproducing on Firefox builds way back to 2014(with many freezes encountered trying to reproduce the issue).

Additional notes

• The following notifications are thrown in the Browser console e.g. "PopupNotifications._onButtonEvent: Button click happened before the security delay: 118.62146261427552ms" when Allow Location Access will be selected.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:csasca, if you think that's a regression, then could you try to find a regression range in using for example mozregression?

Comment 2

[Johann Hofmann [:johannh]]

That functionality is broken in Chrome for me as well, so this seems like a case for developer outreach.

The following notifications are thrown in the Browser console e.g. "PopupNotifications._onButtonEvent: Button click happened before the security delay: 118.62146261427552ms" when Allow Location Access will be selected.

This should be unrelated and shows up because you were answering the prompts too quickly (it's a security feature) :)

Thanks!

Comment 3

[Sylvestre Ledru [:Sylvestre]]

Johann, are you sure about the Product/component? Seems incorrect to me.

I think it should be in Webcompat, don't you think?

Comment 4

[Johann Hofmann [:johannh]]

As I mentioned, it doesn't work in Chrome either, so at best this is web-compat when it's working in Edge only or something? It seems just broken to me.

Comment 5

[Augusto Pace]

This issue was reproducible on Windows 10 with Firefox Nightly version 74.0a1 (2020-01-14) (64-bit).

Comment 6

[Clara Guerrero ( Need Info Brindusa Tot Please)]

This issue was reproducible on Ubuntu 16 with Firefox Nightly version 75.0a1 (2020-02-19) (64-bit)

Comment 7

[Clara Guerrero ( Need Info Brindusa Tot Please)]

This issue is reproducible on Windows 10 with Firefox Nightly version 76.0a1 (2020-03-18) (64-bit)

Comment 8

[Marcela (Please NI request to Brindusa Tot)]

This issue is reproducible on Windows 10 with Firefox Nightly version 77.0a1 (2020-04-15) (64-bit)

Comment 9

[Mathew Hodson]

I think this is in the wrong component. It should be in the Web Compatibility product right? That product seems to be where all the activity and "broken in Firefox, works in other browsers" bugs are.

The description for the Developer Engagement product, where this bug currently is, says "requests for events, outreach and demos"

Comment 10

[Marcela (Please NI request to Brindusa Tot)]

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

Comment 11

[Marcela (Please NI request to Brindusa Tot)]

Reproducible on latest Nightly 80.0a1 (2020-07-07) on Ubuntu 18.04.

Comment 12

[Johann Hofmann [:johannh]]

This is not only broken on Firefox but on all browsers last I checked.