Change Details

# Existing behaviour * User Alice uses Vector skin, and can load scripts/styles with `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob uses Vector-2022 skin, and can load scripts/styles with `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * however Bob will **//also automatically//** load any code in their `User:Bob/vector.js` and `User:Bob/vector.css` * Similarly, the default Vector-2022 skin loads **both** `MediaWiki:Vector.css` **and also** `MediaWiki:Vector-2022.css` # Behaviour after site request * User Alice can load styles/scripts on the Vector skin using `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob can load styles/scripts on the Vector 2022 skin using `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * Vector 2022 skin **does not** load `MediaWiki:Vector.css` **but instead only** `MediaWiki:Vector-2022.css` # Impact if no action In late 2023 / early 2024 suddenly users will see "Behaviour after site request". This means site styles would stop loading (if those are being relied on) and many user scripts would suddenly be turned off unexpectedly. # Background This unexpected and strange behaviour is a side effect of the fact that the Vector 2022 and Vector skin used to be the same skin. With T301212, This functionality can now be disabled by a community if desired, by a configuration change to `wgVectorShareUserScripts` # Recommendation It is recommended that communities discuss this change and manage the timeline of this change themselves, notifying any users it might impact to avoid disruption. This is also a good opportunity to encourage housekeeping - e.g. deletion of local skin js/css that is no longer used. A community can decide to do nothing, but this will eventually become the default behaviour so delaying action here is likely to cause more impact to users on the long term. The old/existing behaviour will hopefully be removed by the end of 2023. # Request to communities [] Please decide if it's preferable for your community to do this now. A conversation in community portal may be sufficient. [] Please create a new ticket tagged #wikimedia-site-requests for requesting the disabling of VectorShareUserScripts

# Existing behaviour * User Alice uses Vector skin, and can load scripts/styles with `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob uses Vector-2022 skin, and can load scripts/styles with `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * however Bob will **//also automatically//** load any code in their `User:Bob/vector.js` and `User:Bob/vector.css` * Similarly, the Vector-2022 skin loads **both** `MediaWiki:Vector.css` **and also** `MediaWiki:Vector-2022.css` # Behaviour after site request * User Alice can load styles/scripts on the Vector skin using `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob can load styles/scripts on the Vector 2022 skin using `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * Vector 2022 skin **does not** load `MediaWiki:Vector.css` **but instead only** `MediaWiki:Vector-2022.css` # Impact if no action In late 2023 / early 2024 suddenly users will see "Behaviour after site request". This means site styles would stop loading (if those are being relied on) and many user scripts would suddenly be turned off unexpectedly. # Background This unexpected and strange behaviour is a side effect of the fact that the Vector 2022 and Vector skin used to be the same skin. With T301212, This functionality can now be disabled by a community if desired, by a configuration change to `wgVectorShareUserScripts` # Recommendation It is recommended that communities discuss this change and manage the timeline of this change themselves, notifying any users it might impact to avoid disruption. This is also a good opportunity to encourage housekeeping - e.g. deletion of local skin js/css that is no longer used. A community can decide to do nothing, but this will eventually become the default behaviour so delaying action here is likely to cause more impact to users on the long term. The old/existing behaviour will hopefully be removed by the end of 2023. # Request to communities [] Please decide if it's preferable for your community to do this now. A conversation in community portal may be sufficient. [] Please create a new ticket tagged #wikimedia-site-requests for requesting the disabling of VectorShareUserScripts

# Existing behaviour * User Alice uses Vector skin, and can load scripts/styles with `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob uses Vector-2022 skin, and can load scripts/styles with `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * however Bob will **//also automatically//** load any code in their `User:Bob/vector.js` and `User:Bob/vector.css` * Similarly, the default Vector-2022 skin loads **both** `MediaWiki:Vector.css` **and also** `MediaWiki:Vector-2022.css` # Behaviour after site request * User Alice can load styles/scripts on the Vector skin using `User:Alice/vector.js` and `User:Alice/vector.css` * User Bob can load styles/scripts on the Vector 2022 skin using `User:Bob/vector-2022.js` and `User:Bob/vector-2022.css` * Vector 2022 skin **does not** load `MediaWiki:Vector.css` **but instead only** `MediaWiki:Vector-2022.css` # Impact if no action In late 2023 / early 2024 suddenly users will see "Behaviour after site request". This means site styles would stop loading (if those are being relied on) and many user scripts would suddenly be turned off unexpectedly. # Background This unexpected and strange behaviour is a side effect of the fact that the Vector 2022 and Vector skin used to be the same skin. With T301212, This functionality can now be disabled by a community if desired, by a configuration change to `wgVectorShareUserScripts` # Recommendation It is recommended that communities discuss this change and manage the timeline of this change themselves, notifying any users it might impact to avoid disruption. This is also a good opportunity to encourage housekeeping - e.g. deletion of local skin js/css that is no longer used. A community can decide to do nothing, but this will eventually become the default behaviour so delaying action here is likely to cause more impact to users on the long term. The old/existing behaviour will hopefully be removed by the end of 2023. # Request to communities [] Please decide if it's preferable for your community to do this now. A conversation in community portal may be sufficient. [] Please create a new ticket tagged #wikimedia-site-requests for requesting the disabling of VectorShareUserScripts