Where do we start? Planning and strategery

[dglazkov]

What's the best way to start actual work? I think we should pick a low-hanging fruit HTML element and turn it into a custom element. Someone suggested HTMLMarqueeElement, but that might be too hard?

@domenic @arv

[arv]

Hah!

http://webfx.eae.net/dhtml/xblmarquee/xblmarquee.html

[domenic]

To me, the first step would be a survey of literally every existing element, so we can see what the targets are. For example, we'll immediately find that a large majority of elements have no real capabilities, apart from presentation (and perhaps accessibility role). E.g., <i> is just a <span> with a given default stylesheet. We'll find others that are slightly more interesting, but not by much, e.g. <a>. We'll find others with complex UI, but no real fundamental concepts, e.g. <details>. And others, like form elements, that need new hooks into the platform. It'll also be important to correlate tag names with class names, since there should only be one custom element per class (so e.g. HTMLElement corresponds to many different tags).

Getting a sense of what the landscape is for levels of difficulty seems important, and I think it would be encouraging to knock off a bunch of easier elements, then work our way up through levels of hardness.

[arv]

http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#elements-1

Extracted into a spreadsheet

https://docs.google.com/spreadsheet/ccc?key=0AtiYRsLxmdqUdEJlT2Z2XzlaT2FOdkhYVUhNeVpHY3c&usp=sharing

[annevk]

I cannot edit that.

• <abbr> is maybe also AT.
• <area> has some relationship thing going on.
• For <base> we should first fix base URL bugs in general. Maybe expose property that can be set on documents afterwards.
• <embed> can be like <iframe> (same for <object>, and <object> can be like <embed> or <img>).

[annevk]

Note that as far as rendering goes a lot is explained already in HTML and what's missing is clear from the Rendering section: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html

[arv]

Made the spreadsheet editable by everyone...

[dglazkov]

@annevk, the AT point for <abbr> is very interesting. Setting ARIA roles implicitly is something that we don't have in the platform at the moment.

[dglazkov]

Stupid git question: how do I submit pull reviews for myself? For example, I want to write some skeletal code, but would love for you guys to review before landing.

[mathiasbynens]

@dglazkov Rather than make the changes in the master branch, create a new branch for the change. Then push the branch to GitHub, and you’ll be able to create a pull request for it.

[dglazkov]

@mathiasbynens :raised_hands:

[dglazkov]

Are we using traceur? If so, I just finished implementing <div> :smiley: http://jsbin.com/qurid/2/edit

[domenic]

Dude, where's my align property?? https://developer.mozilla.org/en-US/docs/Web/API/HTMLDivElement

[dglazkov]

@domenic, I deprecated it :stuck_out_tongue:

[dglazkov]

Started splitting this off into specific issues: issue 9, issue 10, issue 11.

[mathiasbynens]

@dglazkov GitHub auto-links to issues if you prefix their IDs with #, e.g. #9, #10, #11.