Note: The bug occurs when we're using the follwing path: HTMLLoader.window.nativeWindow.activate(),calling from the parent (initial) window. By calling window.nativeWindow.activate() directly from the child window, the bug does not occur.