Change Details

### Background There are a dozen or so modules in core that are unused, and also lack any owner. There is no big problem with any one of these, nor would it be worth the proportionate work to remove a single of these only. This task will attempt to sharing and multiplying the impact by doing several in a batch. If one or two of these end up still needed, it'd be fine to simply keep them as-is and move on. The idea is to shake the tree a little and see what's uncontroversial to remove. ### Outcome * Reduce [Size of the startup manifest](https://wikitech.wikimedia.org/wiki/Performance/Guides/Frontend_performance_practices#Size_of_startup_manifest). * Reduce overhead from busywork (style updates, deprecation churn, search results, etc) for code that isn't actually being used. ### Proposal * [ ] Remove `jquery.color`. Pure logic, copied from upstream in 2007, no known issues or need for updates. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 1 gadget, 19 user scripts It's usually graceful to remove if it's only used for the implicit change to animation effects. Check for `colorUtil` references for procedural dependence. * [ ] Remove `jquery.fullscreen`. Stable, copied from upstream in 2013. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer. * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 results It's effectively a vendor-prefix polyfill, which I imagine is largely if not entirely obsolete by now. The caller should be updated to listen to the relevant event directly using plain jQuery core or DOM directly. * [ ] Remove `jquery.form`. Last updated in 2012. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:TranslateSvg (Currently Archived, See T331817) * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 gadgets, 6 user scripts Historically, this was often not used for its ajax purpose, but rather for its `formSerialize()` utility which is just 2 lines stable and inline-able jQuery code nowadays that we can put into a handful of places directly against the jQuery API rather than through this module. If methods like `ajaxSubmit()` or `ajaxForm()` are used, that indicates significant dependence. In that case we may want to reconsider and either keep or e.g. move to a hidden gadget in its entirely to load on-wiki.

### Background There are a dozen or so modules in core that are unused, and also lack any owner. There is no big problem with any one of these, nor would it be worth the proportionate work to remove a single of these only. This task will attempt to sharing and multiplying the impact by doing several in a batch. If one or two of these end up still needed, it'd be fine to simply keep them as-is and move on. The idea is to shake the tree a little and see what's uncontroversial to remove. ### Outcome * Reduce [Size of the startup manifest](https://wikitech.wikimedia.org/wiki/Performance/Guides/Frontend_performance_practices#Size_of_startup_manifest). * Reduce overhead from busywork (style updates, deprecation churn, search results, etc) for code that isn't actually being used. ### Proposal * [x] Remove `jquery.color`. Pure logic, copied from upstream in 2007, no known issues or need for updates. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 1 gadget, 19 user scripts It's usually graceful to remove if it's only used for the implicit change to animation effects. Check for `colorUtil` references for procedural dependence. * [x] Remove `jquery.fullscreen`. Stable, copied from upstream in 2013. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer. * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 results It's effectively a vendor-prefix polyfill, which I imagine is largely if not entirely obsolete by now. The caller should be updated to listen to the relevant event directly using plain jQuery core or DOM directly. * [x] Remove `jquery.form`. Last updated in 2012. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:TranslateSvg (Currently Archived, See T331817) * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 gadgets, 6 user scripts Historically, this was often not used for its ajax purpose, but rather for its `formSerialize()` utility which is just 2 lines stable and inline-able jQuery code nowadays that we can put into a handful of places directly against the jQuery API rather than through this module. If methods like `ajaxSubmit()` or `ajaxForm()` are used, that indicates significant dependence. In that case we may want to reconsider and either keep or e.g. move to a hidden gadget in its entirely to load on-wiki.

### Background There are a dozen or so modules in core that are unused, and also lack any owner. There is no big problem with any one of these, nor would it be worth the proportionate work to remove a single of these only. This task will attempt to sharing and multiplying the impact by doing several in a batch. If one or two of these end up still needed, it'd be fine to simply keep them as-is and move on. The idea is to shake the tree a little and see what's uncontroversial to remove. ### Outcome * Reduce [Size of the startup manifest](https://wikitech.wikimedia.org/wiki/Performance/Guides/Frontend_performance_practices#Size_of_startup_manifest). * Reduce overhead from busywork (style updates, deprecation churn, search results, etc) for code that isn't actually being used. ### Proposal * [ * [x] Remove `jquery.color`. Pure logic, copied from upstream in 2007, no known issues or need for updates. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.color%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 1 gadget, 19 user scripts It's usually graceful to remove if it's only used for the implicit change to animation effects. Check for `colorUtil` references for procedural dependence. * [ * [x] Remove `jquery.fullscreen`. Stable, copied from upstream in 2013. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:MultimediaViewer. * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.fullscreen%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 results It's effectively a vendor-prefix polyfill, which I imagine is largely if not entirely obsolete by now. The caller should be updated to listen to the relevant event directly using plain jQuery core or DOM directly. * [ * [x] Remove `jquery.form`. Last updated in 2012. * [[ https://codesearch.wmcloud.org/search/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&files=&excludeFiles=&repos= | Codesearch Everywhere ]]: 1 reference in Extension:TranslateSvg (Currently Archived, See T331817) * [[ https://global-search.toolforge.org/?q=%5B%27%22%5Djquery.form%5B%27%22%5D&regex=1&namespaces=2%2C4%2C8&title=%28Gadgets-definition%7C.*%5C.%28js%7Ccss%7Cjson%29%29 | Global Search ]]: 0 gadgets, 6 user scripts Historically, this was often not used for its ajax purpose, but rather for its `formSerialize()` utility which is just 2 lines stable and inline-able jQuery code nowadays that we can put into a handful of places directly against the jQuery API rather than through this module. If methods like `ajaxSubmit()` or `ajaxForm()` are used, that indicates significant dependence. In that case we may want to reconsider and either keep or e.g. move to a hidden gadget in its entirely to load on-wiki.