The patches referenced in T224116#5204455 have changed the loading of the extension from synchronous in extensions/FlaggedRevs/FlaggedRevs.php to asynchronous (happening later when the ExtensionRegistry queue is processed).
Tue, May 21
@Krinkle I think the patch above will fix the log spamming and prevent new Echo events from being created with a CommentStoreComment. Faulty events would stay in place but eventually expire and be deleted.
Sat, May 18
Thu, May 16
Wed, May 15
Tue, May 14
Wed, May 8
Echo is now using stylelint, like most (or all) of the other repos.
The patch that was merged was to fix a JS error that occurs on TWN.
I've created subtasks for the actual work. Making this an epic. Not sure where to put it on the board.
@Petar.petkovic Do you still have that notification stuck? If so, do you have an error in the JS console?
This refers to the cucumber browser tests that don't exist anymore.
The ticket as written was invalid since we've introduced new messages that are not shadowed by local overrides.
We've tried embedding SVGs as data-uri, both in text and base64. The markup is sane and works in browsers but gmail doesn't render them.
Tue, May 7
Mon, May 6
Consider SWATing https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/507956 before enabling the experiment.
Fri, May 3
Now it's merged.
The patch failed to merge because of a MobileFrontend selenium test
Apparently fixed in the library but not yet released: https://github.com/JakubOnderka/PHP-Parallel-Lint/issues/125
Thu, May 2
I think I made a mistake here.
Triaging to "future" for the Growth team but it's possible we'll get to it as part of the effort to reduce Echo's backlog.
Wed, May 1
This was deployed to production just now.
The fix for this was deployed to production just now.
About the two pairs of hover in/out events, the browser considers that when a menu option is selected, the cursor is temporarily out of the HTML element and then on it again. This can be seen with option options like "copy", "save link as...", etc.
The link in question is missing the "data-link-id" attribute that is required for us to track it under a symbolic name. Adding now.
enter-question-text is fired only when the textbox goes from empty to non-empty. If it already contains some text because an earlier question was drafted but not submitted, new changes to the text won't fire any event. This was defined as a rule for Help Panel so we know the textbox is interacted with but we don't fire too many events.
Tue, Apr 30
Haven't used it in years. Thanks for cleaning that up.