Mozilla is
constantly responding to community feedback, almost to a fault, encompassing everything from user interface changes, to features requests, to rolling back undesired changes. I would recommend reading more about Mozilla Connect, which I would argue was specifically launched to get ahead of spurious accusations like these. For a big flashy example, their blog post introducing Tab Groups is titled "You Asked for it, we built it", and the first line is "What happens when 4,500 people ask for the same feature? At Firefox, we build it."
Moreover they've revised their Terms of Use following criticism (much of it here on HN), wound down Pocket and Fakespot in response to feedback about these being outside of their core mission, implemented visual search in response to community requests, made it easier to switch between different profiles again based on community requests, added a rollback option for extensions to previously approved versions in response to developer requests, brought back night mode on iOS after having removed it because the community asked for it, changed the design of the iOS toolbar to get rid of the share button, centralized developer support tools in an all-in-one add on hub. And offered extensive explanations when choosing not to implement or maintain features (e.g. Live Bookmark tool).
The trouble with the real work of responding to requests is it's often granular and unsexy, even when examples abound, and it's easy to not know what they're really doing and reach for the pitchfork.
A good place to start is this explainer on all the community feedback they've been taking in: https://blog.mozilla.org/en/firefox/about-mozilla-connect/