In this case TFM is partly composed of >=1 blogs from >1 browser vendors in addition to properties associated with the underlying browser engine which most people don’t directly use or reference by name. No one has actually written T FM.
We'd love to know what we can do better. What are you missing at https://docs.microsoft.com/en-us/microsoft-edge/devtools-gui... ? We lately spent a lot of time re-organising the documentation to cover different use cases, like people wanting introductions or in-depth details getting different starting points. The documenation is even available on GitHub to post issues and ask for features: https://github.com/MicrosoftDocs/edge-developer
I feel bad if my comment came off overly critical. I did see the Edge dev tools docs and they’re substantially better and more thorough than what I’d seen before. I want to recognize that.
I’d need to spend more time looking through the docs to be specific, but the place my comment came from was seeing both Edge and Chrome dev tools docs with a lot deferred but not cross referenced to Chromium, and both having more depth in their respective blogs than dedicated docs.
Admittedly I became accustomed to referencing the various blogs rather than docs, because that’s where I’ve learned the most about the dev tools across the ecosystem.
I’ll definitely spend more time with the mainline docs and give feedback where I think there’s room to improve. Thank you
That’s not true. There are great sources of documentation for anything you use. Scoped down to the specific topic and it doesn’t have to be found in a blog post or stackoverflow answer. Those are the sources that just beat the SEO game.
