Warning Uses Deprecated APIs - warnings

My blog built in Hugo 0.100.0 with Cloudflare Pages. I got warning on PageSpeed because of Uses deprecated APIs.
I searched on their page but I can’t find which part I have to fix or remove. Is there any solution to fix this warning?

Related

mkdocs search plugin suddenly disappeared - any debugging suggestions?

I've been running a (company-internal) site that uses mkdocs, the materials for mkdocs them, and the default mkdocs search plugin.
It all worked fine until some point around the change of year, when the search field suddenly disapeared.. without any obvious thing having changed. The website is being served by a (company-hosted) gitlab instance.. there's no error or warning message during build that seems to relate to this issue.. nor does there seem to be any related error/warning in the javascript console. All this makes it very difficult to know where to start investigating..
Did anybody experience the same? Or do you have suggestions of where I could start looking?
best
Michael
tried to change the order in which plugins are executed, and various search plugin settings - without any effect. Looked for error/warning messages during mkdocs build (via gitlab ci-cd) and in the Javascript console - without success. Where to start?

In which version of MediaWiki came the feature 'page preview'?

We've MediaWiki 1.31.0 installed, but can't find the feature 'page preview', which is described here: https://www.mediawiki.org/wiki/Page_Previews
On this feature-page there's no hint, in which version of MediaWiki this feature was implemented. Can anybody tell me?
This is not core Mediawiki functionality, but implemented via an extension. See here for more information: https://www.mediawiki.org/wiki/Extension:Popups
PS: 1.31.0 has known security issues, you should at least upgrade to 1.31.7

Chrome extension development on Ubuntu is like a pain

I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.

Google Chrome extensions interaction with Native Client Applications

Is it possible to write a Chrome Extension that will interact with a Native Client application?
I use Irssi through the NaCl Secure Shell application, and I would like to write an extension that simply looks for plain URLs and makes them clickable links.
I'm seeing some strange behavior with extensions and NaCl applications, so I wanted to know if this is something that is even possible.
Additionally, if anyone has a more elegant solution to this, please don't hesitate to let me know.
Thanks!
The fact that the NaCl Secure Shell app uses Native Client under the hood shouldn't matter; the page is rendered using standard HTML.
The documentation for Chrome Extensions here says you should be able to inject content scripts into pages with the chrome-extension scheme. I tried it, but it doesn't work. It seems the documentation is incorrect. See http://crbug.com/153245.
As far as I can tell, it is not possible to modify an extension this way. It is possible to communicate with other extensions/apps (see here), but it seems that the application must expose an API to communicate with.
Secure Shell supports clicking links now via Ctrl+Click. it will support OSC+8 in a future release.

Has anyone got a simple step by step Mozilla plugin tutorial

I'm trying to create a Mozilla browser plugin for the sole purpose of detecting with javascript whether or not an application that I have written is installed. This was inspired by another stackoverflow question and answer on a similar subject.
All I want really is a HelloWorld type example as what I need to write will be even simpler than that. There is a lot of information on the Mozilla website, but as a plugin noob and a C++ novice I'm experiencing information overload. I just need a step by step "this is how to create your first simple plugin".
I have already written the IE equivalent by following this ATL tutorial. This is the kind of level of guide that I would ideally like to find.
Please note, this is specifically about Mozilla plugins and not extensions - Googling this subject brings up a lot of information about extensions in addition to plugins.
Here is a step by step guide for how to build the npruntime sample plugin using Visual Studio. When googling for info regarding Mozilla plugin development, search for npruntime. That is the scriptable plugin standard suported by Gecko (Firefox) as well as Opera and Chrome.