Sure, I would like to work on this!
Thank you - This helps a lot!

I've submitted a patch to fix this issue: https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/1230147

Thanks for pointing this out! I’ll double-check my commit and push the missing files if needed.

Patch uploaded to Gerrit: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/1229591

Thanks for the review!

Thanks for closing this! Confirmed that the original issue is resolved.

Okay sure, makes sense
Thanks for the clarification!

I've submitted the patch : https://phabricator.wikimedia.org/T414592

I submitted the patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/1225554 for this task.

Thanks for the review!
I’ve updated the patch to ensure that <math>A{:}B</math> generates <mo lspace="0em" rspace="0em">:</mo> without extra spacing.
I’ll now take a look at T401746 as well.

I've fixed the MathML colon spacing issue by adding explicit lspace and rspace attributes (0.278em) to the colon operator when rendered in native MathML.

I've fixed the npm lockfile issue by migrating wdio-mediawiki to use the npm workspace protocol. This prevents LibUp and npm update from attempting to replace the local file reference with the registry version.

i've added the necessary i18n message keys for the continuous research recruitment survey and successfully tested the implementation locally.

I've submitted a patch to reduce the excessive vertical whitespace between PersonalDashboard modules:

Thanks!
Happy to help move this forward. Let me know if you'd like me to make any adjustments to the patch.

I've upgraded the vendored Codex Design Tokens from v1.6.1 to v1.18.0 using the update-codex.sh script. All builds and tests pass successfully.

Hi, so now I updated the patch to use only LESS variables from the vendored Codex design tokens!

Thanks for the clarification, Zoe!

Hi! Thank you for the approval.
I plan to contribute to MediaWiki core, VisualEditor, frontend components, and related tooling/build pipelines on Wikimedia GitLab.
I'm still exploring the ecosystem and may expand to other repos as I progress.
Thanks again!

I’ve submitted a patch to address this issue:
https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/1224555

I’ve implemented a fix that addresses the root cause of the RangeError: Invalid time zone specified seen on older browsers.
Summary of changes:
Primary fix: Updated offsetToZone() in DateFormatter.js to return 'Etc/GMT' for a zero offset instead of generating 'Etc/GMT±0', which is not recognized by Chrome 65–66.
Defensive fix: Wrapped the Intl.DateTimeFormat constructor in a try–catch to gracefully fall back to the system timezone if an invalid timezone identifier is ever encountered.
Tests: Added coverage to verify correct handling of a zero offset.
Testing:
All npm tests pass (136/136)
Manually verified diff pages render correctly with timestamps
No RangeError observed in older browsers
Patch: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1224121
Happy to adjust anything if there are concerns with the approach.

(Adding: thanks for clarifying the LESS mechanism — I’ll wait for your guidance before making further changes.)

Thanks for taking a look! I'm happy to make any changes needed to ensure compatibility with standalone mode. Let me know if you'd like me to adjust the patch or if you'll handle it.

I submitted a patch for review:
https://gerrit.wikimedia.org/r/c/VisualEditor/VisualEditor/+/1223698

I've submitted a patch to fix this issue:
https://gerrit.wikimedia.org/r/c/VisualEditor/VisualEditor/+/1222800