Bug 558436 - Postfix content proposal is enabled in existing workspaces, but disabled if restoring defaults
Summary: Postfix content proposal is enabled in existing workspaces, but disabled if r...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.14   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 11:54 EST by Andrey Loskutov CLA
Modified: 2023-11-30 12:59 EST (History)
1 user (show)

See Also:


Attachments
screenshot before / after restore defaults (141.28 KB, image/png)
2019-12-18 11:54 EST, Andrey Loskutov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Loskutov CLA 2019-12-18 11:54:02 EST
Created attachment 281264 [details]
screenshot before / after restore defaults

See bug 558434 comment 4. I have never enabled "Postfix" proposals, but they were ON in my existing workspace. Clicking on "Restore Defaults" shows them deselected. 

One from this both statements is a bug.

If the "Postfix" proposals were supposed to be enabled by default - then they should remain enabled after "Restore defaults".

If they shouldn't be enabled by default - then we should make sure it also works for existing workspaces (see bug 550226).
Comment 1 Dani Megert CLA 2019-12-19 03:28:34 EST
It was enabled by default for a while.

When we changed the default we did not want to change it for existing workspaces where it was enabled and users could use/see the feature.
Comment 2 Eclipse Genie CLA 2021-12-09 07:20:28 EST
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 2023-11-30 12:59:35 EST
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.