VisualEditor/2012-13 Q2 forward-look
Priorities for this quarter[edit | edit source]
- Getting the APIs finished (so other people can more easily get involved)
- Improve stability of the core platform on our target browsers (so it works when we…)
- Deploy in some form to production in a way that lets test users edit real content
Browser matrix[edit | edit source]
- This is not final, but work-in-progress for the VE team; data current as of end-September 2012.
|Overall share||Version||Share||Overall share||Version||Share||Overall share||Version||Share|
|Android||N/A||Less than 0.1%||0.40%||4.3||— ✔||8.64%||4.3||0.31% ✔|
|4.2||0.06% ✔||4.2||1.18% ✔|
|4.1||0.14% ✔||4.1||3.52% ✔|
|4.0||0.14% ✔||4.0||1.45% ✔|
|Less than 0.1%||2.3||1.94%|
|Chrome||33.93%||32.0||0.06% ✔||N/A||Less than 0.1%||N/A||Less than 0.1%|
|Firefox||11.66%||27.0||0.02% ✔||N/A||Less than 0.1%||0.04%||Less than 0.1%|
|4.0||0.37%||Less than 0.1%||5.0||0.11%|
|MSIE||15.17%||10.0||6.55% ✔||0.24%||8.0||0.18% ?||0.03%||Less than 0.1%|
|9.0||2.91% ✔||Less than 0.1%|
|Opera||1.53%||12.16||0.96% ✔||N/A||Less than 0.1%||1.17%||11.10 (Mini/7.5)||0.32%|
|12.15||0.17% ✔||11.10 (Mini/7.1)||0.22%|
|Less than 0.1%||11.10 (Mini/4.2)||0.16%|
|Safari||2.36%||0.0||2.36% ✔||0.36%||iPad||4.16% ✔||1.63%||iPhone||8.09% ✔|
|Less than 0.1%||0.0||0.36% ✔||0.0||1.09% ✔|
|iPod||0.51% ✔||Less than 0.1%|
- This includes Chromium, Chrome's open source version, which identifies as "Chrome" in its user agent.
- This is very suspicious, and is probably mostly mis-placed Firefox clients.
- This looks to be a data corruption error; probably "Mozilla 5.0 (compatible, ...)".
- Including iPod, iPad and iPhone as appropriate.
- Android – 4.0+ (no current automated testing)
- Android before v. 3.0 does not support ContentEditable, so we will have to fall back to wikitext editing.
- Chrome – 19.0+; 29.0+ actively tested
- Chrome has auto-update (but rapid version increases); VE team roughly intend to actively support only the current, soon-to-be-current, and two immediately previous versions, though we intend for all versions at 19.0 and above to work without issue (including forks like Iceweasel). Versions below 19.0 may be possible to support if necessary.
- Firefox – 15.0+; 23.0+ actively tested
- Firefox has auto-update (but rapid version increases); VE team roughly intend to actively support only the current, soon-to-be-current, and two immediately previous versions, though we intend for all versions at 15.0 and above to work without issue (including forks like Iceweasel). There are some technical issues that prevent Firefox 10.0 to 14.0 from being removed from the blacklist; these are solvable if necessary (see bug). Versions below 10.0 lack necessary technological support. Firefox ESR is supported only if the underlying version is supported, so Firefox ESR 10 is not currently supported, but Firefox ESR 17 and Firefox ESR 24 should work fine.
- Mozilla – No support
- Mozilla itself is an ancient browser, and cannot be supported due to technological issues. Lots of browsers are mis-reported as Mozilla but are in fact much more modern, and should work without issue.
- MSIE (Internet Explorer) – 9.0+ (currently suspended)
- Each version of MSIE is differently broken, and adds significant support burden. However, as it is still relatively popular, the team intend to support 9.0 and upwards. Versions below 9.0 suffer from a a variety of missing key technologies which mean they cannot be made to work with VisualEditor.
- Opera – 12.00+ (no current automated testing)
- Opera Desktop (from 12.00 onwards) is a cousin of Chrome, and should work without incident. Opera Mini does not support contentEditable, so VisualEditor can never work on it.
- Safari – 5.0+ (no current automated testing)
- Safari Desktop is a cousin of Chrome, and should work without incident. Safari on iOS (iPad/iPhone/iPod) has very wide-spread auto-update; VE team roughly intend to actively support only the current, soon-to-be-current, and immediately previous version only.
Removed from plan[edit | edit source]
- C++ implementation for December
- We have decided to focus on the Node/JS prototype of the Parsoid for the December release as we do not expect to have the C++ version ready by then.
- C++ implementation for December
- Table editor
- Due to the unexpected difficulties encountered, we do not expect to ship additional node handlers (for other content types) before December, including tables.
- Table editor
- Due to the unexpected difficulties encountered, we do not expect to ship additional node handlers (for other content types) before December, including citations.
- Due to the unexpected difficulties encountered, we do not expect to ship additional node handlers (for other content types) before December, including definition lists.
Areas of work[edit | edit source]
Open Questions[edit | edit source]