We don't have it in Wikibase itself so far for two reasons:
- Wikibase should not have any knowledge about special properties. Here it would have to know that some properties turn their value into links. We'd like to avoid this as much as possible.
- We didn't have a proper way to store the URL used for expanding the identifier. We have that now with statements on properties.
So we will need to figure out a way to do that in Wikibase as well but I am not sure how yet. Until then it'd be good to get this working with the gadget.
It should be possible to migrate this Gadget into a module and add the dependencies: AuthorityControl[ResourceLoader|default|dependencies=wikibase.api.RepoApi]|AuthorityControl.js
Another way would be to add a wrapper JS module for it (to make sure, that the dependencies are loaded) and load the Gadget with mw.loader.load( 'gadget-url' );
But it should be configurable to be a specific module for wikidata.
Mobile has no plans to support global site gadgets right now. They make it really difficult to debug issues and lack a code review process which is pretty important when it comes to exposing JS code to mobile users.
I think if we can find a way to do this on the backend in a generic way this would be the best solution for the long term lifespan of this project.
Yep but no easy way of setting that target. I guess what I'm saying is I discourage the use of a global gadget on mobile. User scripts are fine but I think we have to be more responsible when considering the quirks, performance issues and capabilities of mobile phones.
wikibase.api.RepoApi looks like it's safe to slap a mobile target on it and load it on demand - after it's mibilified, the above change should just work. However, for me this gadget doesn't work in Chrome even on desktop.