Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

Update docs to say ::shadow and /deep/ are deprecated in Polymer 1.0 #1188

Closed
sorvell opened this issue Jun 12, 2015 · 3 comments
Closed

Update docs to say ::shadow and /deep/ are deprecated in Polymer 1.0 #1188

sorvell opened this issue Jun 12, 2015 · 3 comments
Assignees
Milestone

Comments

@sorvell
Copy link

sorvell commented Jun 12, 2015

Here: https://www.polymer-project.org/1.0/docs/devguide/styling.html#xscope-styling

Note, users are still trying to use these features. We support them but they should be considered deprecated.

@sorvell
Copy link
Author

sorvell commented Jun 12, 2015

They are being removed from the cross scope styling spec, and Chrome may deprecate them soon.

@wuyizi
Copy link

wuyizi commented Aug 20, 2015

This is happening: https://www.chromestatus.com/feature/6750456638341120
I am on chrome 45 beta and seeing warnings already from mostly all polymer based web sites (e.g. elements.polymer-project.org).

Those warnings are probably from these files:
https://github.com/PolymerElements/paper-styles/blob/master/classes/shadow-layout.html
https://github.com/PolymerElements/iron-flex-layout/blob/master/classes/iron-shadow-flex-layout.html

@frostius
Copy link

frostius commented Sep 3, 2015

From 1.0 styling guide:

/deep/ ... For the reasons above, the Polymer team is currently exploring other options for theming that address the shortcomings above and provide a possible path to obsolescence of /deep/ and ::shadow altogether

Custom CSS mixins... Polymer includes an experimental extension

So, /deep/ is deprecated, css mixins are experimental. Where does that leave us? The polymer elements seem to be all-in on @apply. Can we get either a commitment on long-term support for mixins or an update on the "possible path" mentioned above?

I need to fix my current /deep/ usages, but I'd really hate to do it more than once. If this is already documented and I missed it, please point me in that general direction - thanks!

@arthurevans arthurevans added this to the Q4S4 milestone Nov 5, 2015
@arthurevans arthurevans modified the milestones: Q4S5, Q4S4, Q4S6 Dec 8, 2015
@arthurevans arthurevans modified the milestones: 2016Q1S1, Q4S6 Jan 15, 2016
@arthurevans arthurevans modified the milestones: 2016Q1S2, 2016Q1S1 Jan 25, 2016
arthurevans pushed a commit that referenced this issue Feb 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants