User Details
- User Since
- Dec 16 2014, 6:43 PM (234 w, 6 d)
- Availability
- Available
- LDAP User
- Mhurd
- MediaWiki User
- Unknown
Wed, Jun 12
Now live at staging! http://appservice.wmflabs.org/en.wikipedia.org/v1/page/talk/User_talk:Brion_VIBBER
Regarding future use of the endpoint for article talk pages, things look pretty ok... I found and fixed one bug, but otherwise, with the exception of the giant templates at the top of some articles, things looks pretty much as expected:
Just a heads-up, per @bearND after the endpoint is merged (at which point it's immediately available in staging here http://appservice.wmflabs.org/en.wikipedia.org/v1/page/talk/User_talk:Brion_VIBBER) they still have a couple (relatively minor) things on their end that need to happen before it will appear in production restbase:
- write swaggers spec
- some restbase code to expose the endpoint
Tue, Jun 11
Thu, May 30
Happening to me too:
Wed, May 22
Hehe ya generally I don't understand why hardcoding table heights would ever be a good idea...
May 17 2019
This is happening on mobile web as well. PageLib/PCS may not be the best places to fix this.
May 14 2019
May 13 2019
May 11 2019
May 10 2019
WIP on my fork:
May 7 2019
May 6 2019
@cmadeo on the endpoint side, for superscript/subscript, I don't think it would be too tough to preserve them. I'm unsure though how tricky the native side handling of this would be though... hopefully not too bad... iirc attributed strings have a baselineOffset property which may help.
May 3 2019
@Jdlrobson This endpoint doesn't post/write.
Apr 30 2019
Per Johan:
Apr 29 2019
Apr 26 2019
Apr 25 2019
@JMinor Joe had a performance fix (linked above) but there was still some question as to whether it still needs a spinner...
Apr 16 2019
Apr 15 2019
Apr 12 2019
Apr 11 2019
Reminder: only needs to work against mobile-html:
https://en.wikipedia.org/api/rest_v1/page/mobile-html/Dog
Assuming the body is present (would have to be to get offsets) the method I was thinking about would be similar to...
getSectionHeadingsData(body: HTMLBodyElement)
...and would return data structured the way @Dbrant specified.
Still ok if I take a stab at this?
@bearND oh cool! will check it out!