Node children using top_level appear differently in-editor vs. runtime.

[donn-xx]

This image shows how in the editor, the position of things is different to when it runs. This seems a bit weird to me.

I was pointed to the cpp which shows this might be intended:
https://github.com/godotengine/godot/blob/4363ae34fa3f52223ae78ff2f2c187ab99827e3a/scene/3d/node_3d.cpp#L736-L749

void Node3D::set_as_top_level(bool p_enabled) {
	ERR_THREAD_GUARD;
	if (data.top_level == p_enabled) {
		return;
	}
	if (is_inside_tree() && !Engine::get_singleton()->is_editor_hint()) {
		if (p_enabled) {
			set_transform(get_global_transform());
		} else if (data.parent) {
			set_transform(data.parent->get_global_transform().affine_inverse() * get_global_transform());
		}
	}
	data.top_level = p_enabled;
}

If this is not going to change, how does one handle the discrepancy in normal use?

I made a small repo if anyone wants to try it:
https://gitlab.com/dbat/top-level-issue

[donn-xx]

Was curious, so I altered the code above to:
if (is_inside_tree()) { // && !Engine::get_singleton()->is_editor_hint()) {
Recompiled and tried my test project. No difference. I don't know why that test for is_editor_hint is in there, but I'm not a dev on this level.

[donn-xx]

I made an issue for this.

godotengine/godot#84290