Bug 1179623 - No alert when closing editors with unsaved changes
Summary: No alert when closing editors with unsaved changes
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER5
: 6.1.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-07 08:52 UTC by Zuzana Krejčová
Modified: 2020-03-27 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:07:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1034734 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1042508 0 medium CLOSED Guided Editor - when closing as asset always asks "Are you sure you want to discard unsaved data" even if nothing has be... 2021-02-22 00:41:40 UTC

Internal Links: 1034734 1042508

Description Zuzana Krejčová 2015-01-07 08:52:25 UTC
Description of problem:
Certain editors don't display the alert ("Are you sure you want to discard unsaved data?") when you try to close them and still have some unsaved changes.
Editors affected by this:
  External imports
  default text editor (pom.xml, package-names-white-list, kmodule.xml, kie-deployment-descriptor.xml)
  Globals Definitions
  Guided Score Cards


Version-Release number of selected component (if applicable):
6.1 ER3


Steps to Reproduce:
1. Open one of the editors.
2. Make a change. (Don't save.)
3. Close the editor.


Actual results:
No alert.


Expected results:
Alert asking for confirmation ("Are you sure you want to discard unsaved data?").


Additional info:
For the External imports editor, this also affects the Project Editor. When a change is made in the Imports section of it and a build requested, the editor does not ask whether to save the changes.


Note You need to log in before you can comment on or make changes to this bug.