# Existing bejaviour
* User Bob can load styles/scripts on the Vector 2022 skin using User:Bob/vector-2022.js and User:Bob/vector-2022.css
* User Bob can load styles/scripts on the Vector skin using User:Bob/vector.js and User:Bob/vector.css, however these will also be loaded on Vector 2022 skin.
* Similarly, the Vector 2022 skin loads MediaWiki:Vector.css and MediaWiki:Vector-2022.css
# Behaviour after site request
* User Bob can load styles/scripts on the Vector 2022 skin using User:Bob/vector-2022.js and User:Bob/vector-2022.css
* User Bob can load styles/scripts on the Vector skin using User:Bob/vector.js and User:Bob/vector.css
* Vector 2022 skin **does not** loads MediaWiki:Vector.css and MediaWiki:Vector-2022.css
# backgrond
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 skin js/css that is unused.
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.
# 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