Bug 533400 - [projection] Collapsed field declarations fold again upon expansion
Summary: [projection] Collapsed field declarations fold again upon expansion
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.8   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-09 22:52 EDT by Evan Bailey CLA
Modified: 2022-10-26 19:12 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Evan Bailey CLA 2018-04-09 22:52:13 EDT 
When a code fold containing several final static comma-separated variable declarations and initializations is collapsed using Ctrl + Shift + / and I try to expand it using the + icon, the contents still exists but disappears visually. When I force it to reappear by backspacing into it and then proceed to collapse it, it shows up with a - instead of a +.
Comment 1 Dani Megert CLA 2018-04-10 09:35:52 EDT 
Those comma-separated fields should probably not be folded in the first place.
Comment 2 Eclipse Genie CLA 2020-08-21 13:06:10 EDT 
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.
Comment 3 Eclipse Genie CLA 2022-10-26 19:12:22 EDT 
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.