Affected versions

• Firefox ESR 60.7.2
• Firefox 67.0.4
• Firefox 68.0b12
• Firefox 69.0a1

Affected platforms

• macOS 10.13
• macOS 10.14

Steps to reproduce

1. Start Firefox
2. Enter https://www.office.com/?omkt=ro-ro
3. Login with a valid account
4. Click on Forms from the Applications category
5. Click on new form and select Add New
6. Click on any of the shown selections, for example "choice" or "rating"

Expected result

• A new form is being added in the document.

Actual result

• Nothing is happening by clicking on any of the available selections

Regression range
I will search for a regression if there is one ASAP. It is not a recent regression as it happens on Firefox 66.0.

Notes

• Please see the attachment for the actual result: https://drive.google.com/open?id=1CApdgLWurqbKfoAvSbKOZ7URSJi6lG9j

[Tracking Requested - why for this release]:

I saw some discussion on the Enterprise list that sounded similar to this, and those issues apparently resolved themselves eventually (i.e. MS fixed something on their end). Does this still reproduce for you?

I tried again on Firefox 68.0b12 and macOS 10.14 and it is still reproducing unfortunately.

Bugbug thinks this bug is a regression, but please revert this change in case of error.

We have contacted Microsoft about this issue. Since this is affecting ESR 60, it is unlikely to be a recent product change that would explain this regression (if the regression is recent), a website change seems more likely.

Catalin, is this a dupe of Bug 1560273? It sounds similar to me, but that bug says it does not reproduce in 67+.

Hi Mike, they seem to be similar, but they have very different outcomes. Bug 1560273 only affects ESR and when selecting "add new" option, the user is greeted with a “Sorry, something went wrong. Please try again.” page message.

This one lets you access forms but can't interact with any of the options available and this affects only macOS, no messages in browser console.

Please let me know if you need any other informations regarding the issue. Thanks!

I tested on Firefox 69.0a1 and macOS 10.13.6 and it works properly.

(In reply to John Dai[:jdai] from comment #8)

I tested on Firefox 69.0a1 and macOS 10.13.6 and it works properly.

FWIW, I got expected results as John.

Catalin, does this still reproduce for you?

Tracking this for now though it seems pretty unlikely that a fix is going to come from our side.

I tried reproducing the issue on Firefox 68.0, latest Nightly 69.0a1 (2019-07-03) and ESR60.8.0, and it seems that the issue has been fixed.