Changing subject since this seems not related to FormItem right? to see what's happening and understand the problem and find a solution we should look at:
* generated HTML: since all in Jewel is CSS based, what is the html output? The way I think Royale works (for Basic, Jewel,..), is that adding a bead in MXML will be added to the beads array. I think the other bead is not removed and still is there, but the new one takes precedence and when component ask for the layout bead it gets the latest. Maybe this is a problem related to the way Royale manage beads, or is a problem to Jewel not updating correctly css selectors. El sáb., 26 ene. 2019 a las 11:46, Piotr Zarzycki (< [email protected]>) escribió: > Carlos, > > I discovered also one more bug or at least I'm thinking about that as a > bug. Having following code [1] does work, but if I add bead dynamically - > it doesn't work. [2] - I believe fix can be placed in method > beadsAddedHandler > - Do you think this is a bug and fix can be here ? > > [1] https://paste.apache.org/IvoK > [2] https://paste.apache.org/kyfP > > Thanks, > Piotr > -- Carlos Rovira http://about.me/carlosrovira
