search

webcomponents / webcomponents.github.io

WebComponents.org is where community-members document Web Components best practices
http://webcomponents.org
733 stars 126 forks source link

Add @josh's interview #149

Closed zenorocha closed 9 years ago

zenorocha commented 9 years ago

So what do you think @josh, @robdodson, @addyosmani?

sindresorhus commented 9 years ago

:+1:

addyosmani commented 9 years ago

Left some comments but otherwise LGTM.

robdodson commented 9 years ago

LGTM after the above comments are addressed.

josh commented 9 years ago

O man, didn't realize it was going to be published as is. All the edits welcome!

zenorocha commented 9 years ago

Did an ammend commit for those minor reviews, now comments are gone - sorry about that =/

zenorocha commented 9 years ago

I'm glad we have history in email format :)

@addyosmani said:

Might be worth including an example here of how you're using the noscript tag for fallback. I've been doing similar and find it super useful!

@josh replied:

For the time element stuff, the inner "noscript" content is just a human readable date string.

unnamed

One draw back here is that since the custom upgrade process is async, theres an noticeable FOUC when the plain text is converted to a relative date. The two texts often have different widths so it often affects line wrapping.

In other cases for select controls, maybe you'd do something like

<x-select>
  <select>
    <option ...>
  </select>
</x-select>

Or even just use the is extension.

<select is="github-select">
  <option ...>
</select>

I'm really liking is as a way to extend existing controls. Typically we'd just do that with a custom class name, but the custom element lifecycle hooks are wonderfully useful.

zenorocha commented 9 years ago

Published: http://webcomponents.org/articles/interview-with-joshua-peek/ ;)

zenorocha commented 9 years ago

https://github.com/webcomponents/webcomponents.github.io/commit/684096086823290d12ccbff7c623c8c2d78d7ef6