You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Piotr Zarzycki (JIRA)" <ji...@apache.org> on 2017/06/01 11:41:04 UTC

[jira] [Updated] (FLEX-35318) [MDL] Components loosing default css style once they pass through native MDL library upgrade

     [ https://issues.apache.org/jira/browse/FLEX-35318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Zarzycki updated FLEX-35318:
----------------------------------
    Description: 
Each component in FlexJS including those from MDL library has his own default css class. Through css class we can apply to component some default behavior using classes like Beads, Models, Controllers or apply some initial style. 

Example of default CSS class for MDL List:
{code}
List
{
    IBeadView: ClassReference("org.apache.flex.mdl.beads.views.ListView");
    IBeadModel: ClassReference("org.apache.flex.html.beads.models.ArraySelectionModel");
    IBeadLayout: ClassReference(null); 
    IDataProviderItemRendererMapper: ClassReference("org.apache.flex.html.beads.DataItemRendererFactoryForArrayData");
    IItemRendererClassFactory: ClassReference("org.apache.flex.core.ItemRendererClassFactory");
    IItemRenderer: ClassReference("org.apache.flex.mdl.itemRenderers.ListItemRenderer");
}
{code}

Created List in MXML or AS code should have in HTML assigned css class "List".

Pseudo code:
{code}
<div class="List"></div>
{code}

Unfortunately Native MDL library components has special life cycles which they are pass through once component is placed in HTML DOM. - I will call it "Upgrading". 

 In the results of upgrading component in HTML code look a bit different than we did create it in AS code. It can gets additional container etc. *Once such List pass through "Upgrading" it does not have their default style.*

As part of this jira I'm going to fix this issue implementing mechanism which assign default css style class once component finish upgrading.



  was:
Each component in FlexJS including those from MDL library has his own default css class. Through css class we can apply to component some default behavior using classes like Beads, Models, Controllers or apply some initial style. 

Example of default CSS class for MDL List:
{code}
List
{
    IBeadView: ClassReference("org.apache.flex.mdl.beads.views.ListView");
    IBeadModel: ClassReference("org.apache.flex.html.beads.models.ArraySelectionModel");
    IBeadLayout: ClassReference(null); 
    IDataProviderItemRendererMapper: ClassReference("org.apache.flex.html.beads.DataItemRendererFactoryForArrayData");
    IItemRendererClassFactory: ClassReference("org.apache.flex.core.ItemRendererClassFactory");
    IItemRenderer: ClassReference("org.apache.flex.mdl.itemRenderers.ListItemRenderer");
}
{code}

Created List in MXML or AS code should have in HTML assigned css class "List".

Pseudo code:
{code}
<div class="List"></div>
{code}

Unfortunately Native MDL library components has special life cycles which they are pass through once component is placed in HTML DOM. - I will call it "Upgrading". 

 In the results of upgrading component in HTML code look a bit different than we did create it in AS code. It can gets additional container etc. *Once such List pass through "Upgrading" do not have their default style.*

As part of this jira I'm going to fix this issue implementing mechanism which assign default css style class once component finish upgrading.




> [MDL] Components loosing default css style once they pass through native MDL library upgrade
> --------------------------------------------------------------------------------------------
>
>                 Key: FLEX-35318
>                 URL: https://issues.apache.org/jira/browse/FLEX-35318
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Apache FlexJS 0.8.0
>            Reporter: Piotr Zarzycki
>            Assignee: Piotr Zarzycki
>
> Each component in FlexJS including those from MDL library has his own default css class. Through css class we can apply to component some default behavior using classes like Beads, Models, Controllers or apply some initial style. 
> Example of default CSS class for MDL List:
> {code}
> List
> {
>     IBeadView: ClassReference("org.apache.flex.mdl.beads.views.ListView");
>     IBeadModel: ClassReference("org.apache.flex.html.beads.models.ArraySelectionModel");
>     IBeadLayout: ClassReference(null); 
>     IDataProviderItemRendererMapper: ClassReference("org.apache.flex.html.beads.DataItemRendererFactoryForArrayData");
>     IItemRendererClassFactory: ClassReference("org.apache.flex.core.ItemRendererClassFactory");
>     IItemRenderer: ClassReference("org.apache.flex.mdl.itemRenderers.ListItemRenderer");
> }
> {code}
> Created List in MXML or AS code should have in HTML assigned css class "List".
> Pseudo code:
> {code}
> <div class="List"></div>
> {code}
> Unfortunately Native MDL library components has special life cycles which they are pass through once component is placed in HTML DOM. - I will call it "Upgrading". 
>  In the results of upgrading component in HTML code look a bit different than we did create it in AS code. It can gets additional container etc. *Once such List pass through "Upgrading" it does not have their default style.*
> As part of this jira I'm going to fix this issue implementing mechanism which assign default css style class once component finish upgrading.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)