#1788 - Support HTML.next and ECMAScript.next (idea staging issue)
-
By Chris Graham
- Added
- 4 views
| Identifier | #1788 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Support HTML.next and ECMAScript.next (idea staging issue) |
| Status | Open |
| Tags |
Risk: Breaks themes (custom) Roadmap: ongoing (custom) Roadmap: Over the horizon (custom) Type: JavaScript (custom) Type: Standards compliance (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | This issue discusses assorted functionality from HTML and JavaScript standards, or proposed standards, that are not yet available for us to deploy.
Once available either #2005 should be updated, or a new issue created. ~~~~ Context menus (see #2442 and https://www.sitepoint.com/whats-new-in-html-5-1/) <details> and <summary> elements for use with Comcode 'hide' tag (see https://www.sitepoint.com/whats-new-in-html-5-1/) Allow new form elements or parameters in fields and forms APIs, e.g. for 'month' inputs Use screenshot API for rendering block widgets in the WYSIWYG editor (i.e. a block would show as a screenshot of how it looks, without all that HTML dumped inside the editor) Tie into native syntax highlighting for 'code' Comcode tag, without need for Geshi addon (see https://www.w3.org/wiki/HTML/next#Syntax_highlighting_for_.3Ccode.3E_elements) Use native WYSIWYG for quick reply (low-bloat, fast, but simple upgrade over textarea) (see https://www.w3.org/wiki/HTML/next#.3Ctextarea_type.3D.22wysiwyg.22.3E) Use Combobox in place of our own manual one (see https://www.w3.org/wiki/HTML/next#ComboBox) Mark up quote/cite attributions correctly in Comcode output (see https://www.w3.org/wiki/HTML/next#Attribution_element_for_blockquote.2C_q_and_cite) Mark up locations using new element (see https://www.w3.org/wiki/HTML/next#.3Clocation.3E_element_.28like_.29_for_expressing_geo_information.2C_eg_with_attributes_lat.2C_long.2C_altitude) Default function parameters (see https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Functions/default_parameters). Other features of ECMAScript.next that improves our code standards (as legacy JS code is always messy and we want to do what we can to clean it up). ~~~~ We won't be using TypeScript/Babel/CoffeeScript/Dart - it's very important to not make webmaster-life/hosting difficult by being early adopters of complex stacks. |
| Steps to reproduce | |
| Additional information | RESOURCES
--------- HTML... https://www.sitepoint.com/whats-new-in-html-5-1/ https://www.w3.org/wiki/HTML/next JavaScript... ECMAScript 5 https://gist.github.com/sym3tri/2425983 ECMAScript 6 http://es6-features.org/ ECMAScript 7 https://pawelgrzybek.com/whats-new-in-ecmascript-2016-es7/ Mozilla https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/ECMAScript_Next_support_in_Mozilla General release notes... Chrome https://developers.google.com/web/updates/ Firefox https://www.mozilla.org/en-US/firefox/53.0/releasenotes/ Comparison tables... http://caniuse.com/ |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments