You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@royale.apache.org by GitBox <gi...@apache.org> on 2018/05/04 18:48:18 UTC

[GitHub] piotrzarzycki21 opened a new issue #222: MDL Components do not accept dynamically changing className after native MDL library upgrade

piotrzarzycki21 opened a new issue #222: MDL Components do not accept dynamically changing className after native MDL library upgrade
URL: https://github.com/apache/royale-asjs/issues/222
 
 
   Each MDL component is passing through upgrading which in some cases adding additional container which is not part of Royale.
   
   **Having following code:**
   ```
   <js:View>
        <mdl:NavigationLayout currentState="Examples" className.Examples="examplesBackground"> 
       </mdl:NavigationLayout> 
   </js:View>
   ```
   **Should be translated to:**
   ```
   <div>
      <div class="examplesBackground"></div>
   </div>
   ```
   
   BUT after translation it looks like that:
   <div>
      <div class="mdl-layout__container"> - This ELEMENT is not a Royale creation. It doesn't have  royale_wrapper.
           <div class="examplesBackground"></div>
       </div>
   </div>
   
   In the results of switching to between different states which are changing `className`, `UIBase` is calling property `parent`. Unfortunately since parent is not an Royale component parent is undefined all the time.
   
   ```
   <mdl:NavigationLayout currentState="Snippets" className.Snippets="snippetsBackground"> 
       </mdl:NavigationLayout> 
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services