Change Details

**Steps to replicate the issue** (include links if applicable): * Go to https://m.mediawiki.org/wiki/Special:Contributions/Hamdsaif * notice the duplicate headers '1 March 2023' above '18 February 2023' and '11 February 2023' above '9 February 2023' **What happens?**: Double date headers on mobile (presumably do to the Flow edits?) **What should have happened instead?**: no double date headers **Software version** (skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.): Chrome 110.0.5481.153 (Android) {F36907849}

**Steps to replicate the issue** (include links if applicable): * Go to https://m.mediawiki.org/wiki/Special:Contributions/Hamdsaif * notice the duplicate headers '1 March 2023' above '18 February 2023' and '11 February 2023' above '9 February 2023' **What happens?**: Double date headers on mobile (presumably do to the Flow edits?) **What should have happened instead?**: no double date headers **Software version** (skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.): Chrome 110.0.5481.153 (Android) When inspected the following HTML is present: "<!-- Could not format Special:Contribution row. -->" This inline comment was added by @Ladsgroup in 1c5ea186263c but I'm not sure I understand the circumstances in which it occurs. {F36907849}

**Steps to replicate the issue** (include links if applicable): * Go to https://m.mediawiki.org/wiki/Special:Contributions/Hamdsaif * notice the duplicate headers '1 March 2023' above '18 February 2023' and '11 February 2023' above '9 February 2023' **What happens?**: Double date headers on mobile (presumably do to the Flow edits?) **What should have happened instead?**: no double date headers **Software version** (skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.): Chrome 110.0.5481.153 (Android) When inspected the following HTML is present: "<!-- Could not format Special:Contribution row. -->" This inline comment was added by @Ladsgroup in 1c5ea186263c but I'm not sure I understand the circumstances in which it occurs. {F36907849}