861997 - Improve live sample system to support Web Components

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: Editing, defect, P3)

Description

[John Karahalis [:openjck]]

What problems would this solve?
===============================
The live sample system does not currently have good support for web components, a feature the DevHub team needs.

Who would use this?
===================
Primarily the DevHub team, but any author should be able to use this feature.

What would users see?
=====================
I am not entirely clear on what would be needed from a user interface point of view, but Dan can probably say more.

What would users do? What would happen as a result?
===================================================
See above.

Is there anything else we should know?
======================================

Comment 1

[Eric Shepherd [:sheppy]]

What do you mean by "web components"?

Comment 2

[Daniel Buchner [:dbuc]]

This bug is kind of a moot point, because it is only applicable to non-wiki pages, which are exempt from the security issues that we normally face on wiki pages. The bug is self-completing once the static pages feature is finished.

Comment 3

[Les Orchard [:lorchard]]

Is there a bug for the "static pages feature", so we can mark this one as blocked by it? Otherwise, we need more details as to precisely what the live samples system is missing that would support Web Components.

Comment 4

[Luke Crouch [:groovecoder]]

I think the "static pages" feature is wrapped up in external source content zones, right?

I.e., if we can make a devhub zone using sphinx, we can put whatever "live samples" we want into it?

Comment 5

[Eric Shepherd [:sheppy]]

This would also obviously be useful for us to document Web Components properly, which we need to be able to do at some point.

Comment 6

[Jean-Yves Perrier [:teoli]]

What is the expected time to land for web components? 6 months? I saw some progress one month ago on <template> (which will be supported out of the box by our Live Sample system), but given the activity on the bug it is very unlikely to be on a release this year.

What would be interesting is the ability to share Web Components between live samples.
We have this need for our tools: we could share our custom widgets between the different tools.

Comment 7

[John Karahalis [:openjck]]

Thanks for bringing this up, Jean-Yves.

Before we communicate a release date for the feature, we need to break it down into a smaller pieces, equal in size to the average card on the Kanban board (keeping in mind that some of the cards on the current Kanban board are unusually big). Luke, can you help us do this?

Comment 8

[Daniel Buchner [:dbuc]]

(In reply to Jean-Yves Perrier [:teoli] from comment #6)
> What is the expected time to land for web components? 6 months? I saw some
> progress one month ago on <template> (which will be supported out of the box
> by our Live Sample system), but given the activity on the bug it is very
> unlikely to be on a release this year.

This is incorrect: <template> is currently implemented in Firefox, Chrome, and Opera. The rest of the Web Components specs are landing in Firefox in the coming months, and Chrome is unprefixing Shadow DOM next month.

Comment 9

[Jean-Yves Perrier [:teoli]]

As said, we don't need to do anything for <template>, it is already supported by our Live Samples.

And "in the coming months", means 2014 for the mimimum. It is not even in Nightly

I think we should not move anymore on this until it is completely in a release.

Don't forget, we can't use <template> in production in a Web site until IE supports it.

Comment 10

[Luke Crouch [:groovecoder]]

DEFLECTION:

:dbuc, is there a wiki page or a bug that tracks the web components that will land in which releases? 

That will help us plan both the docs content for them, and thereby the tweaks we need to make to the live sample system to support them.

Comment 11

[Jean-Yves Perrier [:teoli]]

I'm following the bugs. I have a list of what have landed until now (in Fx 22). Nothing more will be on Firefox this year (unless a big surprise, as Gecko 26, last version for 2013 reach feature freeze tomorrow and the relevant code is not yet reviewed). There are some exceptions to this feature freeze but nothing that we should take into account in something more than risk management.

For the features that will reach production in 2013 we don't need any specific Kuma features. Basic documentation will just need the live sample feature and what we have now.

That's just HTML and a bit of DOM extensions.

Comment 12

[Daniel Buchner [:dbuc]]

(In reply to Luke Crouch [:groovecoder] from comment #10)
> DEFLECTION:
> 
> :dbuc, is there a wiki page or a bug that tracks the web components that
> will land in which releases? 
> 
> That will help us plan both the docs content for them, and thereby the
> tweaks we need to make to the live sample system to support them.

I'd like to avoid iframes because it messes with the demo-ability of components, but I guess we can just open them on a separate page, right? (I believe some demos already do this?)

Comment 13

[ali spivak]

Bumping this, reviewed on 1/10/2014. Dan, can we get an update on Web Components? Is this still a priority for your team?

Comment 14

[ali spivak]

Won't fixing unless someone reopens