Lists reset position from 2.0 projects

[Alzter]

Expected Behavior

Loading a 2.0 project in Scratch 3.0 will keep the lists in the same position as they were in the 2.0 projects in 3.0.

Actual Behavior

The lists reset position loading a 2.0 project in Scratch 3.0.

Steps to Reproduce

Load a Scratch 2.0 project that has visible lists in Scratch 3.0

Operating System and Browser

Windows 10, Google Chrome

(Side note, lists also now always appear on top of things so masking lists like you could in 2.0 by partially covering them is now not possible, and this breaks basically every 2.0 project that uses this technique. Even if they were able to be covered they'd need to be the same size as 2.0 lists down to the pixel to keep the mask effect working correctly. Please fix!)

[towerofnix]

(Side note, lists also now always appear on top of things so masking lists like you could in 2.0 by partially covering them is now not possible, and this breaks basically every 2.0 project that uses this technique. Even if they were able to be covered they'd need to be the same size as 2.0 lists down to the pixel to keep the mask effect working correctly. Please fix!)

What you're describing is #1397 (but it is a pretty old issue and so probably won't be addressed/re-evaluated until after the 3.0 release).

[Alzter]

But why not now? I find it's very important to have 3.0 run 2.0 correctly, I mean isn't that one of the things it, I don't know, NEEDS to do? It would be too late to fix this post release, all the 2.0 projects would be broken by then anyway. I think it's much more important to fix incompatibilities BEFORE the release, not after, even if that means delays. I mean do you really think it's a smart idea to rush the release of 3.0 resulting in a ton of 2.0 projects being broken? Isn't it a better idea to make it WORK first? Is that too much to ask?

[Alzter]

2.0

3.0

This NEEDS to be fixed unless you WANT to break projects.

Side note: why is the stage so jittery/blurry?