The new API browser.menus.overrideContext is announced with documentation links pointing to blogs, including a personal blog page with unrelated Japanese texts and anime pictures. The official documentation (MDN) has no reference to the new features. Even the API features from FF63 (august 2018) are only have a draft of documentation (e.g. Menus.getTargetElement). Documentation is important, even more for an API. I think this pattern is worrying.
That's the blog of the developer of Tree Style Tabs, who is presumably Japanese. I agree that it would be nice to have such information on MDN, and since MDN is a wiki, anyone here can do it if they feel strongly enough about it. The linked blog post contains a wealth of information describing how the API works, along with links to further explanatory posts.
Yeah, the feature is not introduced that well. It is mostly a good feature for the extension that they are talking about, TreeStyleTab[1], which explains the feature. Piro's blogpost is actually awesome. It describes the history of the feature, and how it is used today in his extension.
However, they could stand do the documentation themselves, or at least setting up the context of the blog-post a little more.
I am not worried by the reference to the post, Piro may not have the most pretty site, but his writeups are great!
In this case, I don't care much if the blog is pretty or not and who wrote it, even if Tree Style Tabs is my main reason for using Firefox. The problem is that Firefox is relying on an external source as the main explanation of their new API. Will the URL still be right in a few months? They have no control over it.
MDN is one of the best achievements of Mozilla, so I worry when I see it is not updated with their own technologies.
As mentioned above, piro_or is the developer of the popular extension this feature was tailor-made for. I imagine it is well-documented on their site because they were closely involved in the development. I see no reason not to presume the documentation hasn't been added to the wiki yet simply because the devs were working down to the wire to get it included in this release as many users have been clamoring for it. In fact, there is a fairly detailed blog post on Mozilla's site that suggests this is the case.[1] All the worst-case assumptions about Mozilla on this site are getting tiresome.
