I ran into this the other day but dodged around it and didn't look into it further until now.
It might be that we shouldn't set as many properties in the * selector. I think I saw somewhere else that other "browser" stylesheets have defaults for each component and don't rely on *. The key piece, I think, is that inherited properties in CSS have a lower importance that *. It might be that the CSS lookup in Flex was broken and used * or global as the selector of lowest importance and allowed inherited rules to override *. So, I think the answer may be to set the font in the type-selectors. That's more code to download, but there may not be another way. Olaf, one thing I saw in the Gist is that you are not declaring the ACEEditor in MXML or using it as an Royale component. IMO, that should be the goal, and that would provide you a "type selector" to use to set the default font. I think once you do that, your example will look more like other Royale examples. When we "capture" an existing JS component, we actually wrap it. And the wrapper is where you stick most, if not all, of the the glue code you see in the component's usage example. The key for you may be to defer calls to the ace code until addedToParent() when you know the id of the component. By default, the component will create a div in the constructor and later and give it the id assigned in MXML. HTH, -Alex On 1/2/18, 1:37 PM, "Olaf Krueger" <[email protected]> wrote: >Still no success... other ideas? > >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%7Caharui%40adobe.com%7 >Caa34171fa4a548b1983608d5522905ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7 >C0%7C636505258502363927&sdata=j5eM1iTaU4%2FDrLMGDcwAaLcs7qyTSRYj9Bwhj2yi9P >U%3D&reserved=0
