- From: Kent Wood <notifications@github.com>
- Date: Fri, 09 Mar 2018 00:59:16 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/webcomponents/issues/745/371677675@github.com>
very dispoint to hear that :( if a component can support content inject via slot, however, you just can not define the style of the specific content inside that component directly. it is not cool really. performance or functional, i prefer to first make it functional, then we talk the performance, otherwise, it is just a disability component if there is no directly way, i have to chose 1. define the style inside the injected content ``` <my-navbar> **<style>ul li {color:red}</style>** <ul> <li>link1</li> <li>link2</li> <li>link3</li> </ul> </my-navbar> ``` if i use multi times of the component, means i should add that style defination each time, even that style is fixed, and should be placed in a fixed place (just inside the component). it is just a page size waste of the page which use component 2. just forget the slot function. forget the content inject like a normal component should support in that case, i move the inject directly into the component's render function however, if the inject content is different, means i should create different component. then **my-navbar1,my-navbar2,mynavabar-forhome,mynavabar-forotherpage...** will come out, that is just ungainly it is not possible if i want write a common UI library in that case there should be a way to support inject content style defination gracefully! @hayatoito -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/745#issuecomment-371677675
Received on Friday, 9 March 2018 00:59:41 UTC