Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341099

Summary:	Decide if parts that get closed should get setDirty(false) called on them
Product:	[Eclipse Project] e4	Reporter:	Remy Suen <remy.suen>
Component:	UI	Assignee:	Project Inbox <e4.ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Remy Suen

2011-03-28 09:13:51 EDT

If a dirty part gets closed, the user is prompted as to whether a save should be invoked. If the user picks no, should the framework call setDirty(false) on that part?

Comment 1 Eclipse Genie

2019-01-27 02:57:04 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 2 Lars Vogel

2019-06-05 07:39:04 EDT

This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.