Change Details

Should our shared UI component library continue to support IE11 (and ES5)? **Considerations** * Shared library code will live outside of MediaWiki, meaning it will be easier to use certain build tools to automatically transpile code back to ES5. We won't need to write our component code in ES5. * Regardless of transpilation tools, Vue 3 cannot support IE 11 due to its use of [[ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy | Proxy objects ]] * The WMF has updated its [[ https://www.mediawiki.org/wiki/Compatibility/IE11 | compatibility policy ]] to state that new products don't need to support IE11. Any ResourceLoader modules with the `es6: true` property simply won't be delivered to legacy browsers at all. * There are several existing Vue.js projects that already support IE11 (WMDE features, Commons MediaSearch, etc). What should happen to these features? * IE11 support has significantly tapered off since early 2020 – as of July 2021 we're down to a [[ https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-timeseries | daily average of 0.7% across all sites ]] (desktop and mobile). For desktop traffic alone, the share is only slightly higher at 1.8%. **Relevant Links** - T285045 Consider dropping IE support in WiKit **Decision** TBD

## Summary Should our shared UI component library continue to support IE11 (and ES5)? ## Considerations #### Why does this matter? Shared library code will live outside of MediaWiki, meaning it will be easier to use certain build tools to automatically transpile code back to ES5. We won't need to write our component code in ES5. Regardless of transpilation tools, Vue 3 cannot support IE 11 due to its use of [[ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy | Proxy objects ]]. #### Compatibility policy and IE statistics The WMF has updated its [[ https://www.mediawiki.org/wiki/Compatibility/IE11 | compatibility policy ]] to state that new products don't need to support IE11. Any ResourceLoader modules with the `es6: true` property simply won't be delivered to legacy browsers at all. IE11 support has significantly tapered off since early 2020 – as of July 2021 we're down to a [[ https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-timeseries | daily average of 0.7% across all sites ]] (desktop and mobile). For desktop traffic alone, the share is only slightly higher at 1.8%. #### Existing projects There are several existing Vue.js projects that already support IE11 (WMDE features, Commons MediaSearch, etc). What should happen to these features? #### Relevant Links - T285045 Consider dropping IE support in WiKit --- ## Decisions #### 1. Will the new shared component library support IE, meaning it will need to be built with Vue 2? **Design Systems Team proposal:** See T286948 for further discussion and our proposed path forward. #### 2. What happens to existing projects that support IE? **Design Systems Team proposal:** Provide a no-JS fallback experience for IE users. Some projects, e.g. MediaSearch, already include this for no-JS users, it would just need to be extended to users with no ES6 browser support.

## Summary Should our shared UI component library continue to support IE11 (and ES5)? **Considerations**## Considerations #### Why does this matter? Shared library code will live outside of MediaWiki, meaning it will be easier to use certain build tools to automatically transpile code back to ES5. We won't need to write our component code in ES5. Regardless of transpilation tools, Vue 3 cannot support IE 11 due to its use of [[ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy | Proxy objects ]]. #### Compatibility policy and IE statistics The WMF has updated its [[ https://www.mediawiki.org/wiki/Compatibility/IE11 | compatibility policy ]] to state that new products don't need to support IE11. Any ResourceLoader modules with the `es6: true` property simply won't be delivered to legacy browsers at all. IE11 support has significantly tapered off since early 2020 – as of July 2021 we're down to a [[ https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-timeseries | daily average of 0.7% across all sites ]] (desktop and mobile). For desktop traffic alone, the share is only slightly higher at 1.8%. #### Existing projects * Shared library code will live outside of MediaWiki, meaning it will be easier to use certain build tools to automatically transpile code back to ES5. We won't need to write our component code in ES5. * Regardless of transpilation tools, Vue 3 cannot support IE 11 due to its use of [[ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy | Proxy objects ]] * The WMF has updated its [[ https://www.mediawiki.org/wiki/Compatibility/IE11 | compatibility policy ]] to state that new products don't need to support IE11. Any ResourceLoader modules with the `es6: true` property simply won't be delivered to legacy browsers at all. * There are several existing Vue.js projects that already support IE11 (WMDE features, Commons MediaSearch, etc). What should happen to these features? * IE11 support has significantly tapered off since early 2020 – as of July 2021 we're down to a [[ https://analytics.wikimedia.org/dashboards/browsers/#all-sites-by-browser/browser-family-timeseries | daily average of 0.7% across all sites ]] (desktop and mobile). For desktop traffic alone, the share is only slightly higher at 1.8%. **#### Relevant Links** - T285045 Consider dropping IE support in WiKit --- ## Decisions #### 1. Will the new shared component library support IE, meaning it will need to be built with Vue 2? **Design Systems Team proposal:** See T286948 for further discussion and our proposed path forward. #### 2. What happens to existing projects that support IE? **Decision** TBDsign Systems Team proposal:** Provide a no-JS fallback experience for IE users. Some projects, e.g. MediaSearch, already include this for no-JS users, it would just need to be extended to users with no ES6 browser support.