TODO

  • Revision slug: User:dbruant/TODO
  • Revision title: TODO
  • Revision id: 32706
  • Created:
  • Creator: dbruant
  • Is current revision? No
  • Comment 25 words added

Revision Content

This is my TODO-list of pages i want to change, improve. Feel free to add items (especially in JavaScript and DOM)

ECMAScript

  • Do a page like this one but for JavaScript features.
  • Document this
  • isNaN: explain why it's broken. Introduce Object.is. Clean up the page. File bug on bugs.ecmascript.org about isNaN spec which lies.
  • Improve the NaN page. Clean up, make beautiful, mention "Number.NaN" but stop focusing on it, because it's redondant and more verbose, talk about == and ===.
  • Array: make it awesome. Maybe separate the Array built-in and the array instances. Maybe follow ES5.1 sectionning style because it makes sense. Write a note for PHP devs.
  • instanceof: cleanup page. Remove the XPCOM section, find it a new home, because web devs do not care.
  • foreach: write a polyfill for human beings. Document what callback arguments are! Talk about that. Improve examples.
  • Object.defineProperty: talk about configurable more in details and program robusteness, invariants, etc.
  • delete. Cleanup page
  • Update Proxy doc when the API changes and is implemented on Firefox
  • Describe, when and why s.toUpperCase().toLowerCase() != s.toLowerCase() (also on Manuel_Strehl's mental TODO list)
  • Update Safari 5.1 ES5 compat infos

DOM

  • window.onunload. Explain the unload semantics
  • Maybe ask to stop on-* pages and ask to rather have dom event pages. One not somewhere could explain how to attach event handlers.
  • document.createDocumentFragment: Make it awesome. Add examples. Explain why it's better than appending things on the DOM. Add compat table to show it is supporte on IE6, so no reason not to use!!
  • textContent: Say it's better for performance and security. Add interesting examples for that.
  • document.querySelectorAll: cleanup. say NodeLists aren't live, because it'd be impossible to implement or terrible performance-wise.
  • NodeList & HTMLCollection. Add a section on why they look like arrays but are not (and can't use array extras on it). Talk more about liveness maybe.
  • document.cookie: talk about cookie theft, cleanup. Maybe try to discuss ow to prevent it with some ES5 magics (needs an instance of IE9-10).
  • Not sure what to do with this page
  • element.addEventListener: improve
  • event.relatedTarget drag and drop events are standard since HTML5. Investigate relatedTarget semantics for the different drag events.
  • Improve Creating_and_triggering_custom_events. Talk about CustomEvent (add browser support for this feature as well(FF version: 6)). Discuss usefulness of CustomEvents

Other JS technologies

  • frames. apparently window !== frames on IE8 or something. Investigate & document
  • setTimeout: add a note on the fact that integers are returned as identifers which could be a security issue in cases. show how to have a safe setTimeout/clearTimeout pair. Add a full section on "fast setTimeout 0"

CSS

  • display: document table-related values.
  • Bring to MDN some sort of "definite CSS positionning guide", because this is fucking difficult!
    • Research on the web
    • Find people who know a lot about this topic (maybe the awesome Lea Verou or Robert Nyman)

Other

Revision Source

<p>This is my TODO-list of pages i want to change, improve. Feel free to add items (especially in JavaScript and DOM)</p>
<h2>ECMAScript</h2>
<ul> <li>Do a page like <a href="/User:FreakCERS" title="User:FreakCERS">this one</a> but for JavaScript features.</li> <li>Document <a class=" link-https" href="https://twitter.com/#!/kangax/status/93807138975137793">this</a></li> <li><a href="/en/JavaScript/Reference/Global_Objects/isNaN" title="en/JavaScript/Reference/Global_Objects/isNaN">isNaN</a>: explain why it's broken. Introduce <a class=" external" href="http://wiki.ecmascript.org/doku.php?id=harmony:egal">Object.is</a>. Clean up the page. File bug on bugs.ecmascript.org about isNaN spec which lies.</li> <li>Improve the <a href="/en/JavaScript/Reference/Global_Objects/NaN">NaN</a> page. Clean up, make beautiful, mention "Number.NaN" but stop focusing on it, because it's redondant and more verbose, talk about == and ===.</li> <li><a href="/en/JavaScript/Reference/Global_Objects/Array#Properties_2" title="en/JavaScript/Reference/Global_Objects/Array#Properties_2">Array</a>: make it awesome. Maybe separate the Array built-in and the array instances. Maybe follow ES5.1 sectionning style because it makes sense. Write a note for PHP devs.</li> <li><a href="/en/JavaScript/Reference/Operators/Special/instanceof" title="en/JavaScript/Reference/Operators/Special/instanceof">instanceof</a>: cleanup page. Remove the XPCOM section, find it a new home, because web devs do not care.</li> <li><a href="/en/JavaScript/Reference/Global_Objects/Array/forEach" title="en/JavaScript/Reference/Global_Objects/Array/forEach">foreach</a>: write a polyfill for human beings. Document what callback arguments are! <a class=" external" href="http://www.wirfs-brock.com/allen/posts/166">Talk about that</a>. Improve examples.</li> <li><a href="/en/JavaScript/Reference/Global_Objects/Object/defineProperty" title="en/JavaScript/Reference/Global_Objects/Object/defineProperty">Object.defineProperty</a>: talk about <code>configurable</code> more in details and program robusteness, invariants, etc.</li> <li><a href="/en/JavaScript/Reference/Operators/Special/delete" title="en/JavaScript/Reference/Operators/Special/delete">delete</a>. Cleanup page</li> <li>Update Proxy doc when the API changes and is implemented on Firefox</li> <li>Describe, when and why s.toUpperCase().toLowerCase() != s.toLowerCase() (also on <a href="/User:Manuel_Strehl" rel="custom nofollow">Manuel_Strehl</a>'s mental TODO list)</li> <li>Update <a class=" external" href="http://kangax.github.com/es5-compat-table/">Safari 5.1 ES5 compat infos</a></li>
</ul>
<h2>DOM</h2>
<ul> <li><a href="/en/DOM/window.onunload" title="en/DOM/window.onunload">window.onunload</a>. Explain the <code>unload</code> semantics</li> <li>Maybe ask to stop on-* pages and ask to rather have dom event pages. One not somewhere could explain how to attach event handlers.</li> <li><a href="/en/DOM/document.createDocumentFragment" title="en/DOM/document.createDocumentFragment">document.createDocumentFragment</a>: Make it awesome. Add examples. Explain why it's better than appending things on the DOM. Add compat table to show it is supporte on IE6, so no reason not to use!!</li> <li><a href="/En/DOM/Node.textContent" title="En/DOM/Node.textContent">textContent</a>: Say it's better for performance and security. Add interesting examples for that.</li> <li><a href="/En/DOM/Document.querySelectorAll" title="En/DOM/Document.querySelectorAll">document.querySelectorAll</a>: cleanup. say NodeLists aren't live, because it'd be impossible to implement or terrible performance-wise.</li> <li>NodeList &amp; HTMLCollection. Add a section on why they look like arrays but are not (and can't use array extras on it). Talk more about liveness maybe.</li> <li><a href="/en/DOM/document.cookie" title="en/DOM/document.cookie">document.cookie</a>: talk about cookie theft, cleanup. Maybe try to discuss ow to prevent it with some ES5 magics (needs an instance of IE9-10).</li> <li>Not sure what to do with <a href="/en/DOM/event/Comparison_of_Event_Targets" title="en/DOM/event/Comparison_of_Event_Targets">this page</a></li> <li><a href="/en/DOM/element.addEventListener" title="en/DOM/element.addEventListener">element.addEventListener</a>: improve</li> <li><a href="/en/DOM/event.relatedTarget" title="en/DOM/event.relatedTarget">event.relatedTarget</a> drag and drop events are standard since HTML5. Investigate relatedTarget semantics for the different drag events.</li> <li><a href="/en/DOM/Creating_and_triggering_custom_events">Improve Creating_and_triggering_custom_events</a>. Talk about <a href="/en/DOM/event/CustomEvent">CustomEvent</a> (add browser support for this feature as well(FF version: 6)). Discuss usefulness of CustomEvents</li> </ul><h2>Other JS technologies</h2>
<ul> <li><a href="/en/DOM/window.frames" title="en/DOM/window.frames">frames</a>. apparently window !== frames on IE8 or something. Investigate &amp; document</li> <li><a href="/en/DOM/window.setTimeout" title="en/DOM/window.setTimeout">setTimeout</a>: add a note on the fact that integers are returned as identifers which could be a security issue in cases. show how to have a safe setTimeout/clearTimeout pair. Add a full section on "fast setTimeout 0"</li>
</ul>
<h2>CSS</h2>
<ul> <li><a href="/en/CSS/display" title="en/CSS/display">display</a>: document <code>table</code>-related values.</li> <li>Bring to MDN some sort of "definite CSS positionning guide", because this is fucking difficult! <ul> <li>Research on the web</li> <li>Find people who know a lot about this topic (maybe the awesome <a class=" external" href="http://leaverou.me/">Lea Verou</a> or <a class=" external" href="http://robertnyman.com/2010/02/24/css-display-inline-block-why-it-rocks-and-why-it-sucks/">Robert Nyman</a>)</li> </ul> </li>
</ul>
<h2>Other</h2>
<ul> <li><a href="/User:dbruant/Buzzwords_Explained" title="User:dbruant/Buzzwords_Explained">Page on Buzzwords and what they really mean.</a></li> <li>Some people's daily job is to find out browser bugs and workaround. Like <a class=" link-https" href="https://twitter.com/#!/ie9bugs">ie9bugs</a> or <a class=" external" href="http://jquery.com/">jQuery</a> too. Dig into that and document in relevant places.</li> <li>Make sure all infos from <a class=" external" href="http://www.wait-till-i.com/2011/07/28/call-for-better-web-tutorials/">Chris Heilmann post</a> are on MDN</li> <li>Improve pages by order of <a href="/Special:Popularpages?language=en&amp;limit=200" title="Special:Popularpages?language=en&amp;limit=200">popularity</a></li>
</ul>
Revert to this revision