Polymer: Polymer News ?

[jogibear9988]

Again a question from me about News:

• Is there a Timeplan for the Final Polymer 3 Release? (1 Month, 3 Months, 1 Year?)
• Does anyone answer questions on https://github.com/Polymer/project?
• Will the Roadmap on https://github.com/Polymer/project be refreshed?

[wmginsberg]

Yes! I meant to get around to this this week, but a few things came up. I'll update

[jogibear9988]

thx.

and one more:

• what is planed for shared styles between components?

[web-padawan]

BTW it would be nice to provide some insight from the Chrome dev team on this questions:

• HTML imports end of support date
• Custom elements v0 end of support date
• Shadow DOM v0 end of support date

As we know from this list, lots of Google projects still use 1.x and it would be nice to have at least a specific year, e. g. in the same manner as Adobe recently announced end of life for Flash in 2020.

I'm asking because Polymer is used by some enterprise projects which obviously cannot be "rewritten from scratch every six weeks" (c)

I guess that since 2.0 will be still around at least 1 year or so, HTML imports native support might stay with us longer than e. g. Shadow DOM v0 (which is not used by default as of 1.x)

[petr001]

Any news on releasing Polymer 3? Some new features would really help us, so basic time-frame would be useful.

[web-padawan]

@petr001 as of now, there are two blockers AFAIK:

1. ES modules are still behind the flag in Firefox and Edge, see here
2. dynamic imports are not there yet.

So, it is unlikely that 3.0 will be released soon. Since Polymer team schedule is kinda like event-oriented (Google IO / Polymer summit), we should wait at least until IO 18 I guess.

[jogibear9988]

No News?

[jogibear9988]

@wmginsberg any news? ;-)

[ergo]

@web-padawan I think I've read that chrome team does not remove features unless there is special need for that. You can expect web components v0 will be here for years, since they don't conflict with v1.

[jsilvermist]

@ergo Actually there is at least one conflict that I know of, which is document.createElement()'s 2nd argument taking a string for options in v0, and an object in v1.

For more info, see discussion and links in Polymer/docs#1705.

[jogibear9988]

Info: @Polymer3 is be expected early next year (mentioned here: https://www.youtube.com/watch?v=Wu2GCRkDecI)

[jogibear9988]

@wmginsberg maybe you will find some time? ;-)

[ergo]

Any news on the roadmap?

[TimvdLippe]

Our roadmap has now been updated per https://github.com/Polymer/project/pull/41 Check it out at https://github.com/Polymer/project/blob/master/Roadmap.md It also contains a link to this Polymer 3 timeline.

I will also ask the team what the policy is for answering questions on Polymer/project. Most of the questions should be addressed, but we will get to that if some are not.

[jogibear9988]

@TimvdLippe
Will also the Blog be updatet sometime?

And whats the state of the current polymer lib (not lit)? Will it be discontinued sometime?
Is there a document how to migrate to lit? For example, I have elements wich rely on dom access, wich could also be used with lit, but only after the first render. But I have properties wich use "this.$...", this will fail in lit-elemnt when it occurs before first render. This wasn't an issue in polymer3, so is there a migration suggestion? Or will polymer3 stay here for a much longer time? We really have a huge app, and get no info what is going on.
What about css apply (I know this will not get to us), how should we style webcomponents in the next years... questions over questions?

And what about a polymer summit?

[TimvdLippe]

Please create a new issue. This issue has been closed for more than 2 years.