Thanks @Anomie, that makes sense.
But what is actually stored in the database (SELECT TYPEOF)?
Mon, Nov 18
Sat, Nov 16
Fri, Nov 15
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.
Thu, Nov 14
Wed, Nov 13
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 which 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?
Mon, Nov 11
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%)
Sun, Nov 10
The same seems to be true for enwiki (logged out, private mode, random article):
Fri, Nov 8
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.
Thu, Nov 7
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.
Wed, Nov 6
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).
Tue, Nov 5
Possibly related: T236749
Mon, Nov 4
Sun, Nov 3
Fri, Nov 1
This is possibly related to stashed edits, we might need to reset the limit on parser init, but that needs to be tested.
Thu, Oct 31
Apparently we can't yet use webcomponents in all supported browsers, so this is not the way to go.
Mon, Oct 28
Sun, Oct 27
Sat, Oct 26
This was caused by 1617bb3deb4e6f761caf3a7bfbee338bfbfe502a upstream, needs further investigating.
This is not actionable as is, a similar task can be reopened if there's a more concrete proposal.
Fri, Oct 25
I just purged the page and it is gone now:
That page has almost 700 entity usages:
I talked to @Tarrow about this yesterday and we decided it would probably be better to not use OOUI, but do this with Vue ourselves.
Thu, Oct 24
Maybe OO.ui.PopupButtonWidget is what we should be using?
I just look at this again and it was easy to get this to work, after I figured that we need to specific the init JS in scripts first (before the common one).