They might be connected.  I think the problem we've been discussing is "how 
should the DOM be set up for absolute positioning?".  I don't think there is a 
perfect solution, but using '.Application *' may be good enough for now.

I think you may be describing a different issue which is "how should layouts 
find out about the need to run layout again?".  I don't think there is a right 
answer here either, but PAYG says we shouldn't bake in watching every child in 
the DOM like Flex did.  That's just wasteful.  We could create some bead that 
does that for the general case, or for Express and maybe even Jewel to cut down 
on configuration/debugging, but we should make sure other strategies work, like 
beads that watch a single property on a component (LayoutChangeNotifier).  The 
idea is that someone should only have to pay for watching the things that truly 
matter in layout.

My 2 cents,
-Alex

On 6/5/18, 4:15 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
<carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote:

    Hi,
    
    just let you know that the problem seems a bit close to the one I reported
    about using view states for a new blog example post.
    If I change View layout from Basic to for example VerticalLayout, that
    fixes the issue.
    So in Jewel BasicLayout, that now is based on CSS, I added a loop like in
    the rest of layouts so each chid dispatch "sizeChanged" event
    This fixes the problem.
    So maybe this is not the right fix, but seems that basic layout needs its
    children to "prepare" itself for a change.
    
    Just to let you know since it seems both problems are connected.
    
    Thanks
    
    
    2018-06-05 8:53 GMT+02:00 yishayw <yishayj...@hotmail.com>:
    
    > Alex Harui-2 wrote
    > > UIBase used to set position=relative on all positioners.  We took that
    > > away so that the "flex" and other display/layout styles would not have 
to
    > > deal with the excess clutter and overhead of having set position on so
    > > many elements in the DOM.
    >
    > Can you give an example of excess clutter caused by this?
    >
    >
    >
    >
    > --
    > Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C7544e7d51bcd4246635e08d5cad5a966%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636637941374916636&sdata=rt9%2BTvmMTxoONKGPs28eeW7BBjZ85FicsaMk7ygxno0%3D&reserved=0
    >
    
    
    
    -- 
    Carlos Rovira
    
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7544e7d51bcd4246635e08d5cad5a966%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636637941374916636&sdata=y%2BAUMUakdOYIoVnc1NOYB96AbqgIuzBUoGzQXE6XCLA%3D&reserved=0
    

Reply via email to