The filename of the class(with source code included) should not end with .class on debugging scene

When we normally open a class with source code, its filename ends with .java. However, if we jump to a class with source code during debugging, the filename ends with .class. This results in the same class being opened twice (one ending with .java and the other with .class), which is very confusing. Could we standardize this behavior? If a class has source code, it should always be opened as a file ending with .java.

Meanwhile, a breakpoint has been set in the .java file (the Java source file of the class), but during debugging, the execution jumps to and breaks at the .class file instead. The breakpoint symbol is not displayed, yet it actually takes effect. This issue occurs because the same class has been opened with different file extensions.

Reproduce the debugging navigation with a Java class that has source code and compare the opened .java and .class entries. Trace the source mapping or breakpoint navigation path, then verify that source-backed classes open only as .java files and that breakpoint symbols appear on that file.