Closed attilapuskas closed 6 years ago
Unfortunately, this is needed because of the shady CSS shim (see the "Note" in the https://www.polymer-project.org/2.0/docs/devguide/style-shadow-dom#style-slotted-content-distributed-children chapter)
I guess you wanted to point on that, right?
Note: To work within the Shady CSS scoping shim limitations, and to ensure consistent cross-browser behavior, add a selector to the left of the ::slotted(.classname) notation (for example, p ::slotted(.classname).
If so then I think the .input-wrapper could be a good candidate for such a selector, couldn't it?
I have just realized that the input-wrapper does not provide the split point which we would need to differentiate between the for example the prefix and suffix but what if we move the class="suffix" from the span element to the slot suffix and then use .suffix::slotted ?
When the Polymer 1->2 migration has been done, the prefix and suffix slots got wrapper span elements. (here)
This wrapping breaks at least the previously applied fix with --layout-flex-none because it should be used on the wrapper element.
I have seen no benefit in using such span elements around so I would recommend to remove them and adjust the style accordingly, like: