Thu, Apr 2
@kaldari this seems like a solid plan. Twiddling the CSS seems much more feasible than generating SVG from scratch (scary!).
Wed, Apr 1
Sun, Mar 29
Thu, Mar 26
With all the endpoints done, this epic is done.
@Aklapper It's about doing something similar with the Core REST API. I've added that project as a tag. Thanks for the reminder!
This is a duplicate of T247876
Wed, Mar 25
@BPirkle great implementation, thanks for doing it.
Tue, Mar 24
I moved this from the old Parsoid initiative to the Core REST API initiative.
This is done.
All children done.
Mon, Mar 23
@daniel I would prefer that we make as little as possible required; everything that's required is one more bit of effort on the part of the client developer.
Thu, Mar 19
@daniel I'm reluctant to introduce a requirement for the edit summary at the API layer. I believe it's possible to save a revision with no summary, and it's possible to create a page with no revision summary in the UIs we have, right?
@Pchelolo would you mind reviewing this and see if there's any guidance to provide?
Wed, Mar 18
Tue, Mar 17
Mon, Mar 16
I broke out the user story for reverse proxies to T247779 so we can track that work separately. Let's keep this ticket just about client-side.