JS-rendered timestamps are showing as "Edited by 45 years ago" locally, apparently without regard for whether they have actually been edited.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Add backwards-compat metadata so booleans keep working right | mediawiki/extensions/Flow | master | +30 -5 |
Revisions and Commits
Related Objects
- Mentioned In
- T92917: Flow posts all have "45 years ago" timestamp (IE 11 issue)
rMEXT8bb0eb7c8efb: Updated mediawiki/extensions Project: mediawiki/extensions/Flow…
rEFLW8d0df3958ebe: Add backwards-compat metadata so booleans keep working right - Mentioned Here
- T92917: Flow posts all have "45 years ago" timestamp (IE 11 issue)
T76728: Clean up ApiResult and ApiFormatXml, create new formatversion
Event Timeline
Only applies with https://gerrit.wikimedia.org/r/#/c/182858/ (I happened to have that checked out), but we need to solve this before that can be merged.
The ball is back in our court. For now, we need to use ApiResult::META_BC_BOOLS . See https://gerrit.wikimedia.org/r/#/c/182858/ .
Change 180755 had a related patch set uploaded (by Matthias Mullie):
JS-generated timestamps have no hover, only displays readable time
I don't think so. Also, this bug shouldn't appear on core master yet, only with the patch linked above.
I added this to the sprint, because we're blocking that core change. I don't think it's super high-priority yet (we're not the only thing blocking it), but I don't want to forget about it.
Change 189171 had a related patch set uploaded (by Mattflaschen):
WIP: Add backwards-compat metadata so booleans keep working right
Change 189171 merged by jenkins-bot:
Add backwards-compat metadata so booleans keep working right
An editor says they are still seeing this bug at mediawiki. I'm unable to reproduce, but perhaps it's an IE/Windows specific bug? I've asked for more details at https://www.mediawiki.org/wiki/Topic:Sami9qe4icwmyz4x
This should never have been visible to end users. It was done in preparation for https://gerrit.wikimedia.org/r/#/c/182858/ , which is not yet merged.
If someone's seeing this, it's probably a separate cause, and we need more info to track it down. (Note, I don't see any mention in the OP about locking).
Ah, sorry, I've filed T92917: Flow posts all have "45 years ago" timestamp (IE 11 issue) to cover this new bug.