CODEWITHSUNDEEP
javascriptpolymerpolymer-1.0
Blaze
Blaze

Reputation: 109

Polymer 0.5 and production use

I use some of the polymer 0.5 components in production. In the console are emited some deprications related to deep and shadow dom. So i was wondering if 0.5 components are based on experimental apis? Is it posible that the components brake totally in near future? If this happen, can we force the lib to use the polifil for every browser?

I also see some of this deprications logged in the console when I open the 1.0 polymer components on the polymer.org web page. Are this components also not stable and can have big api changes in neer future?

Tnx Blaze

output in console:

/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details. app.js:418 homepage_elements.vulcanized.js:1 ::shadow pseudo-element is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.

Upvotes: 0

Views: 116

Answers (1)

Günter Zöchbauer
Günter Zöchbauer

Reputation: 657248

Polymer 0.5 uses deprecated CSS selectors. See also https://bugs.chromium.org/p/chromium/issues/detail?id=498405 and the Chrome developers seem to be eager to get rid of it since a while.

I don't know about the strategy for polyfills.

Polymer 1.x also used these selectors for a few things and was working on getting them replaced by newer things. I think they are only rarely or not used at all anymore by the elements provided by the Polymer team https://elements.polymer-project.org/ I don't know about other vendors but I guess they will migrate away from these selectors as well soon.

Polymer 1.x is definitely stable. If you want to use something for production use Polymer 1.x.

Upvotes: 2

Related Questions