Haxe

My reasoning for that is it's also affecting the menubar

These components are getting added to the stage *after* everything else, so there's no reason they should be appearing under them

there has been like 2 core changes in the last few days... none of which i can imagine are doing that

are you sure it wasnt doing it before and you just havent noticed

JS target, which hasn't been touched since I last sent the link

you can go back through the commits via git and see

ie, checkout a specific commit, see if it happens, if not, move back another commit

Might be heaps doing it: <https://github.com/HeapsIO/heaps/commit/4c289005f13779dec246d98363990c76c404d438>

How do I go about setting the libraries to specific commits

so you'd need to check out via git first... and then i think you can just use "git checkout {sha}" (or something similar to go back to specific commit) - if you are using a GUI client it'd be simpler

I get similar behavior going back onto earlier commits

However, I get different behavior if I add the component via going through my Main and adding it to s2d, rather than through ``Screen.instance.addComponent``

what is your "going through my Main and adding it to s2d" doing? How did you init the toolkit?

I have a static variable in main that points to s2d, that way regardless of class I can perform ``Main.rootScene.addChild``

Toolkit is being initialized like so:

```haxe
menu = new MenuMain(s2d);

...

public function new(?_parent:Object) 
    {
        super(parent);
        
        Toolkit.theme = "dark";
        Toolkit.init({
            root: _parent;
        });

          menubar = new MenuBar();
         Screen.instance.addComponent(menubar);

```

if I add the component via my static, the layering woprks as expected

what if you change the init to `root: Main.rootScene`