Software Developer @ Wikimedia Deutschland
Thu, Dec 5
@kai.nissen Fixed that now.
Wed, Dec 4
@JanJaquemot What Edge version did you use here? I cannot reproduce the behavior you described with Edge 44.18362.449.0. It marks the first name field as invalid after the autofill is done but as soon as you click anywhere, the first name field becomes valid. All other fields are correctly marked as valid immediately.
SWAT deployment is done, mobile tracking should start showing data from 12:30 UTC time if all went well.
Tue, Dec 3
Looks good, let's deploy this to production.
@kai.nissen The changes have been merged and you can test it on the test environment.
@kai.nissen Done, I also resolved the merge conflict that we had because of the weird timing with banner 14 and 15, please double-check real quick that I did not break the whole banner while resolving that.
Mon, Dec 2
I think we already do track the form the properly by pushing FormAnalytics::trackFormSubmit to Matomo. I have added a call for FormAnalytics::scanForForms as advised by the Matomo documentation whenever the modal is opened, this could possibly improve the tracking of the form. Full PR is here:
Thu, Nov 28
Ticket is done because there is no data to export ✅ .
Okay, bad news, there is no tracking data at all so far for mobile, neither mobile-en. We are not sure yet why this is happening because the relevant banner code is shared and should work. Unfortunately, there is nothing to be exported here because we have not recorded any data on the mobile banners at all this year. I checked, all other banners are being tracked correctly, though.
@Izno This is for a Wikimedia Deutschland website and unrelated to WMF websites or MediaWiki so that tag is likely not appropriate.
Here's a hotfix:
Probably the same issue as this one: T231319
Wed, Nov 27
Done, I have set it to Friday 11 am UTC and also set the current campaign to expire at that time. Let me know if any more changes are needed, otherwise the banners will go live automagically on Friday.
Tue, Nov 26
Can't reproduce, is this still an issue?
This only seems to occur when compact=1 and fd=1 are active URL parameters. Generally seems a bit buggy on Chrome but since these tests are not active anymore, I guess we will just ignore this for now.