You can't reduce a collection of the priorities of individuals down to a single one. Mozilla doesn't have a single direction in the same way Apple or Google don't have a single direction. You can look at the general goal of pushing the web forward if you want, but that idea has many forms of expression.

The real problem doesn't come from being confused about what Mozilla 'stands for', it's comes from short term thinking by their leadership. Their products are being undermined by a leadership that doesn't understand their potential worth (both in terms of their importance to the web, and financially to Mozilla). Without leadership that looks long term at what benefits the web and has a vision of how to get there, that leadership will mostly be a hindrance. Thankfully the engineering teams seemed to have struck gold with Rust/Servo (and in ASM.JS's influence on WebAssembly), which should serve Mozilla well as the technical basis for future development.