Community
Participate
Working Groups
Since 4.20 (never seen it before) typing some HTML inside a comment behaves very strange: I want to type "This method is only called by <B>Xyz</B>." While typing, the '>' disappears and only reappears when I type on. Contrary: typing code like: "ArrayList<String> u;" behaves normal. I have seen more temporary phenomenons while typing comment, but the '>' case is a steady one. ;JOOP!
I am not able to reproduce it with the 4.20 or latest 4.21 I-build. Please attach a sample project/code and check your content assist preferences to restore them to defaults. Also, try this without any additional plug-ins installed on the SDK.
Can reproduce on OS X 10.14.6 with a freshly downloaded epp.java 2021-06. This is most likely the same thing as bug 574585 / bug 574351. Specific to OS X; seems to have something to do with any kind of braces or other "find a matching close character" like string delimiters or here XML tag delimiters. There's also a noticeable delay on Mac when entering a block-opening {.
BTW, typing "ArrayList<String>" does _not_ behave normally. When I type this (for a new local variable in a method): ArrayList< gets auto-completed to ArrayList<|> with the cursor at |. Now delete the >. Type "String>". When you type the '>', there's a noticeable delay before the character appears, but contrary to the XML example from comment 0 the character does appear without typing anything more.
Quick side note here: I worked with Oliver Drotbohm on reproducing bug 574585, we used the same Eclipse SDK 2021-06, the same JDK, empty workspace, exactly same steps (creating a new Java project, typing the same, etc.) and I wasn't able to reproduce the problem on my side while he could reproduce this reliably every time. So creating an environment that reproduces this might not be as easy as creating a sample project and trying that. One thing that we noticed was a different in the macOS version. I was running Big Sur, while he was running an older version.
In that case .... well, I'm stuck with Catalina. So, there's hope for salvation ... when I buy a new iMac that can run B.Sur. Thanks to all for the answers. ;JOOP!
(In reply to Martin Lippert from comment #4) > Quick side note here: > > I worked with Oliver Drotbohm on reproducing bug 574585, we used the same > Eclipse SDK 2021-06, the same JDK, empty workspace, exactly same steps > (creating a new Java project, typing the same, etc.) and I wasn't able to > reproduce the problem on my side while he could reproduce this reliably > every time. > > So creating an environment that reproduces this might not be as easy as > creating a sample project and trying that. One thing that we noticed was a > different in the macOS version. I was running Big Sur, while he was running > an older version. Just curious: assuming Oliver runs Catalina, which JAVA release? I run JDK 14 on Catalina, but I can't get 15 or 16 to run correctly. ;JOOP!
I tried this on Big Sur and could not reproduce. Moving to SWT to look into OS and version specific details that might be causing this.
Root cause addressed via fix for bug 574351. *** This bug has been marked as a duplicate of bug 574351 ***
