Wed, Feb 5
We should check if this is the case on /page/mobile-html as well.
Thu, Jan 23
Looking forward to this research.
But I'm actually optimistic about this. MediaWiki's ResourceLoader already supports client-side template compilation using Mustache Templates. This works fine and is used in a number of places in production now. The functionality we're talking about here is very similar. Browsers are very good at parsing strings into DOM nodes quickly and efficiently.
Jan 16 2020
Strange, before for me Carnivorous redirected with a 302 to Carnivore and now it is a 200 with type no-extract.
It seems like RESTBase is not resolving the redirects when the request is CORS.
Jan 15 2020
I'm glad a recommendation has been made, and that we can move things forward in other very important topics that maybe are more foundational than the framework, like build tools and processes, and developer workflows. Those decisions will directly affect how any library is used.
We need to discuss with Product and Design if we want to get rid of the whole thing, or leave a UI element to open the whole list of references that were removed, or not if those are available somewhere else.
This may be related to making the request from a different domain with CORS, and the preflight requests and the behavior when a redirect is returned
Jan 8 2020
We discussed it and it seems very hard with the user generated content to put in special behavior with these two because of how some templates behave or how the HTML is produced.
Can Design please sign off that this change is ok for both platforms in terms of color before we get to it?
Dec 18 2019
hey @MSantos, is this a subtask of T238830: Profile proton memory usage for Helm chart?
@Pchelolo Apparently internal services are using https, should we update the node services template to do so in production? Thoughts?
We should also update the markdown tutorial/docs on page library pagelib/docs/pcs/pcs.md.
Let's use the JSDoc format and the tooling/theme for publishing can happen separately.
Dec 11 2019
From grooming discussion: Eventually this component should be updated to use structured data on commons captions whenever there is enough data.
The processing performance seems fine now.
Can you have a look Gergö?
Dec 5 2019
Dec 4 2019
We had an informal conversation about the task discussing the various implementation proposals and details.
This is how the content is stored validted and served in the wiki, it is not mobile-html service's responsibility to clean this.
- What is the behavior when the response has no pages?
- Is there a problem with title normalization?
- Does /page/related support user pages?
Dec 2 2019
Are the old jquery versions dev dependencies of some tool or actual production dependencies deployed to users? Seems important to clarify the origin of those.
Nov 26 2019
@daniel, given the involvement of the job queue and the async job, could we then use the existing summary service, or is that still considered a loop?
Nov 22 2019
I was checking and there is a few requirements of the information a stateless version of the summary endpoint would need:
It seems clear then that 2) is not a feasible implementation no?
The summary as I understand it for the two proposals:
Nov 20 2019
Oct 30 2019
Oct 29 2019
Oct 8 2019
Thanks for your comment! Very much appreciated.
Oct 7 2019
Ping @sbassett who did work on the security review of the service and has context. Thoughts?
To further explain, /page/mobile-html is like a google map embed, or a youtube video embed, but with wikipedia content in a mobile-friendly way, so it would be super interesting to enable safe embedding on the web if it is possible.
Made open sub-tasks orphan, they can be found under the Product-Infrastructure-Team-Backlog with the PCS filter
Oct 2 2019
Oct 1 2019
Sep 18 2019
Hey @MSantos, this seems fixed AFAIK, resolve the task if it is. Thanks!