Somehow the code review for the changes in the popup extension part seems to be stalled. The last comment seems more general and thus, the patch will probably rot away unless there is a more abstract discussion about it beforehand. Unfortunately, it is not clear to me who is in a position to decide on features for the popup extension.
Regarding the remotely related tasks listed below, I have the respective comments:
- T199096 We need a popup that is triggered when hovering formulae and displays information from the MathApi. While this information originates from Wikidata I do not see how this helps... (PS: Q1/2018 is over)
- T233099 yes, but I can't do it!
Copy of the comment from Gerrit:
Jdlrobson Sep 10 11:40 PM Patch Set 2: Code-Review-1 Hey there! Thanks for the contribution. Given this is about obtaining content I feel the gateway related code needs to go in the service layer in the API query itself. My worry with the client side approach is we'll add more client gateways for each bespoke problem we encounter. We specifically avoided the mediawiki api for the page previews feature as it's not able to handle the production levels of traffic it gets. Performance aside, I believe we should be striving to keep the page previews client code as light as possible since it loads on every page view. Instead, I would suggest we follow up with https://phabricator.wikimedia.org/T199096 and incorporate this in the summary API for wikidata.org. Once that's in place a small client change in the render layer to deal would wire up the Math elements and hit the wikidata.org summary endpoint. The rendering layer would be adapted to do the rest.
