Mon, Jan 27
Tue, Jan 21
Mon, Jan 20
The patch up now doesn't change the visible behaviour, as it still explicitly untaints the statement once the edit is cancelled. Changing that behavior (so that the statement will be shown as tainted still) is just a matter of deleting a line now, though.
Fri, Jan 17
Fri, Jan 10
Thu, Jan 9
Wed, Jan 8
I think we're done as far as this task goes, the popper is now a easily-reusable component within our source tree (pulling it out would be trivial, but is out of scope here).
Dec 17 2019
Dec 16 2019
Dec 13 2019
I just talked to @Tarrow about this, and for now it should be enough to use that new component directly in App.vue, but if that turns out to bloat App.vue to much we will revisit this.
Dec 12 2019
Dec 11 2019
Dec 9 2019
Dec 6 2019
@Tarrow Can you link the respective changes here?
Dec 4 2019
Dec 2 2019
Nov 28 2019
So I just looked into this a bit and sadly this is not a trivial change. First of all, I don't think we want to expose backlinks (as in Special:WhatLinksHere) as these don't have the semantics the use cases here call for (and using them still would probably lead to strange behavior in the long run). That's because these are just all links pointing to a page, no matter where these originate from: statement (main) values, reference values, qualifier values (and probably even more).
Nov 22 2019
Nov 21 2019
I think this is actually fully done by now.
Nov 20 2019
Nov 19 2019
Thanks @Anomie, that makes sense.
But what is actually stored in the database (SELECT TYPEOF)?
Nov 18 2019
Nov 16 2019
Nov 15 2019
I think we're done here, the popper is now properly mounted to the tainted icon. Everything else (styling, wording, …) is out of scope for this task.
Nov 14 2019
Nov 13 2019
Note: We decided to wrap mw.track in a Vue component now. I made some initial progress here and will (hopefully) finish that tomorrow.
So bridge uses a ServiceContainer to hold (as 'tracker') a mw.track instance. They use that, via their EventTracker and via DataBridgeTrackerService. We should probably do the same or something similar, although we can probably get away with a little less abstraction?
Nov 11 2019
I purged all pages from above (which haven't been re-parsed since) and gathered new numbers:
- The average PC size is 101219.66 (down ~2.7%)
- The median PC size is 68137 (down ~7.2%)
- The minimum PC size is 12911 (down ~3.1%)
- The maximum PC size is 393856 (down ~1.4%)
Nov 10 2019
The same seems to be true for enwiki (logged out, private mode, random article):
Nov 8 2019
I just implemented it like this, but I'm not sure that's going to suffice… if the user clicks on the popper, this will probably also trigger the blur and thus close the popper. Maybe if the popper is a direct child of the TaintedIcon <a> this will work, but I'm not sure.
Nov 7 2019
So apparently OOUI sets tabindex="0" on the constraints icon, with that we can actually focus (and thus also handle blur). I'll do the same for us in order to re-implement the behavior as closely as possible.
Nov 6 2019
I have a patch that wires up the "x" to close the popper, I didn't yet look into closing it if the user clicks onto something else.
I collected some data about the parser cache sizes of the ruwiki pages with the most hits this month (as per stats.wikimedia.org).
Nov 5 2019
Possibly related: T236749