Community
Participate
Working Groups
Created attachment 273929 [details] Screen shot Build ID: I20180409-2000 Steps to reproduce: 1. Double click eclipse.exe file 2. Create a JUnit Jupiter Test Case without added JUnit 5 library to build path 3. Open the JUnit Jupiter test, click @Test annotations, then click Ctrl+1 4. Verify the Quick Fix proposal on @Test annotations Problem Description: "Press 'Tab' from proposal table or click for focus" is truncated.
Does this only happen with this Quick Fix?
(In reply to Dani Megert from comment #1) > Does this only happen with this Quick Fix? Hi Dani, Other Quick Fix shows the same string. E.g. the quick fix when package is not included.
This is like that since 2008 and no complain from a real user so far. Workaround is to increase the size of the Quick Fix/Assist window.
(In reply to Dani Megert from comment #3) > This is like that since 2008 and no complain from a real user so far. It's alright to defer it. > Workaround is to increase the size of the Quick Fix/Assist window. Let me clarify that the message "Press 'Tab' from proposal table or click for focus" won't be shown after increasing the Quick Fix/Assist window manually. So it's not a workaround for the user.
(In reply to You You from comment #4) > > Workaround is to increase the size of the Quick Fix/Assist window. > > Let me clarify that the message "Press 'Tab' from proposal table or click > for focus" won't be shown after increasing the Quick Fix/Assist window > manually. > So it's not a workaround for the user. You need to resize the window with the Quick Fixes. Yes, that will close the help, but you can select another Quick Fix in the window and the help will appear with same size as the Quick Fix window. Also, the size is stored, so next time it will have the new size for the Quick Fix window and the help.
Thanks, Dani. I finally understand the workaround. Resize the Quick Fix proposal (which was shown after clicking Ctrl+1), the the size is stored and applied to the help window. =)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
