Ah, I didn’t see that. Thanks
Why is this marked resolved/fixed? This is still the case as of 26.3 snapshot 4
Ah, I didn’t see that. Thanks