Note that the issue reproduced on Edge v.16, which was not based on Chromium, maybe that is the reason it doesn't reproduce now.