Fri, Feb 15
Mon, Feb 11
It seems to be deployed with the latest Puppet run. Thank you!
Sat, Feb 9
Stretch grid is now available. I have just opened a task to ask the upgrade of the tesseract packages to the latest version from Stretch backports: T215693
Thu, Feb 7
The feature is behind a configuration variable disabled by default. This change uses <maplink> instead of <mapframe> so the output is still a textual display of the coordinates, but now with a link that opens a Kartographer map. So, nothing should break except if some modules parses the output (but hopefully they all use #property for that)
Wed, Feb 6
Tue, Feb 5
A 303 answer looks like a good option indeed.
@Lydia_Pintscher Do you think we could close this task? All basic features seems done and deployed on wdqs.
Wed, Jan 23
Sun, Jan 20
I should close the other task, sorry
Jan 17 2019
Jan 16 2019
Thank you! It's perfect for now!
Jan 14 2019
Seems to be solved.
Jan 11 2019
Jan 10 2019
Jan 9 2019
Dec 20 2018
Dec 19 2018
Dec 11 2018
@Lydia_Pintscher Maybe review https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikisource/+/408365 and try to push the security review of the Wikisource extension to get it deployed on beta then production cluster.
Dec 6 2018
Nov 29 2018
I believe everything has been converted. We still have T146160 opened, but it's not related to HTML input elements.
@bd808 Thank you very much for having had a look at it! I believe that waiting for Stretch deployment is indeed the easiest way to go.
Nov 27 2018
Nov 22 2018
For this task to be done, the extension should be deployed on Wikisource: T210174
Nov 21 2018
Nov 20 2018
Great idea! I'll be very happy to +2 a change.
Nov 19 2018
Nov 17 2018
@TheDJ getSelection is overrided to support Wikitext to VE switch. We should definitely make header/footer compatible with textSelection. I have not taken time to implement this change yet. But if someone could write it, it would be much appreciated.
Nov 10 2018
I just had a quick review of the current GraphQL structure for Wikibase entities. It looks great! Thank you!
Nov 7 2018
Thanks! The current task seems to duplicate that one indeed.
Oct 25 2018
Oct 16 2018
So you're not really asking for a change in the JSON-LD, you're asking for wikidata to only emit a single entity on the /entity/* endpoint -- and that would/could apply to all the different representations using the purtle backend. That's not a JSON-LD specific request.
@daniel We could do something similar for stubs. with structures like:
Not a problem but a cosmetic proposal: Instead of having the structure:
@Reedy Should we close this task? The related change have been merged