display:none is hooked up to the visible property. You can use states to change the visible property. IncludeIn/ExcludeFrom should operate on the DOM since there is no "property" that affects that.
We could introduce an "includeInLayout" property that affects visibility:hidden, but I found that includeInLayout was abused in the past and led to poor performance. If you set the currentState to a non-existent state, the default statesimpl should not have code to check for that since by the time you go into production, you should have all of that worked out. We could provide a debug-mode StateImpl that does check for valid inputs. Debug-mode beads would be helpful in lots of cases. -Alex On 10/19/17, 2:23 PM, "Olaf Krueger" <[email protected]> wrote: >>States removes element from DOM > >I wonder why Royale states removes element from DOM instead of using the >CSS >properties >visibility:hidden; (The element is hidden but still take up the same >place) >or display:none (The element is hidden and take up no space); > >Does somebody know what is the benefit of removing elements from DOM vs >the >use of CSS? > >However, I think if Royale states are working in a similar way as in Flex >this would be one more key feature of Royale. > >Thanks, >Olaf > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy >ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%7C329fcc20a026465f7 >e7e08d51737b127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364404503298 >29149&sdata=4J9Q2htwS4ShLHzA4tUx1nt1loqy0UwitdO3vYCZadg%3D&reserved=0
