m.facebook.com - Unable to trigger "Category" and "Locations" menu pages

[softvision-oana-arbuzov]

URL: https://m.facebook.com/marketplace/selling/item/

Browser / Version: Firefox Nightly 210315 (🦎 88.0a1-20210313094300)
Operating System: Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density), Google Pixel 5 (Android 11) - 1080 x 2340 pixels, 19.5:9 ratio (~432 ppi density)
Tested Another Browser: Yes Chrome

Problem type: Site is not usable
Description: Buttons or links not working
Steps to Reproduce:

1. Navigate to https://m.facebook.com/marketplace/selling/item/
2. Tap "Category" menu.
3. Observe behavior.

Expected Behavior:
"Category" menu page is triggered.

Actual Behavior:
Nothing happens, "Category" menu page is not triggered.

Notes:

1. The issue is also reproducible for "Location" menu.
2. The issue is not reproducible on Chrome.
3. Workaround: Tapping fast "Category" or "Location", the menu pages are triggered.

Watchers:
@softvision-oana-arbuzov
@softvision-raul-bucata

View the screenshot

Browser Configuration

• None

From webcompat.com with ❤️

[karlcow]

I get a Marketplace Isn't Available to You

[karlcow]

So I can't steal this from @ksy36

[ksy36]

This appears to be not working because pointer-events: none on both Category and Location elements. If I disable the rule, the categories open up.

Strangely the issue is not reproducible on RDM. I'll try to create a reduced test case.

[ksy36]

This appears to be not working because pointer-events: none on both Category and Location elements. If I disable the rule, the categories open up.

Ok, this is only half accurate as I was tapping on the label of the field (i.e. "Location"); if I actually tap on the field itself (i.e. "Toronto"), it still doesn't work.

I came up with a reduced test case https://codepen.io/ksy36/pen/JjpZzRG. It looks like the root cause is the fact that disabled input is not responding to mouse events/taps, which is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1653882.

[hsinyi]

This seems to be fixed to me.