Bug 157678 - [Dialogs] Global preference to disable Modal Dialogs
Summary: [Dialogs] Global preference to disable Modal Dialogs
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 14:58 EDT by Gary Karasiuk CLA
Modified: 2019-09-06 16:15 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Karasiuk CLA 2006-09-18 14:58:58 EDT
We are running into all sorts of automated testing problems, because various components pop up modal dialogs. When this happens the testcase just hangs, since there is no user there that can respond to it. 

To make our product more testable, there should be a global preference (or environment variable) that all components check, and when set, they don't pop up modal dialogs. 

This would be a special setting that we would use when running automated tests, and wouldn't normally be turned on when a user was using Eclipse.
Comment 1 Chris Laffra CLA 2006-09-18 15:42:06 EDT
Alternatively, we could have our own special version of jface Dialog that APT shut s down automatically. OR, we run a special thread that closes any open dialog box it finds withing 500ms.
Comment 2 Chris Laffra CLA 2006-09-18 22:06:47 EDT
My last comment may need some explanation :-)

I was referring to an internal tool we use in IBM. A general Eclipse solution would be good, as Gary suggests.
Comment 3 Susan McCourt CLA 2009-07-09 17:18:25 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:15: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.