Apache OpenOffice (AOO) Bugzilla – Issue 11779
warning dialog does not get launched when confirm in case of other document sources is set on
Last modified: 2003-06-12 14:18:18 UTC
SFrameworkInstall.jar.21.02.2003, staroffice 644 build m. Tested on Solaris 9. Deploy a script to a document and create a binding for it.e.g. testbind.sxw Select tools, options, security. Ensure the run macro option is set to path. Set the confirm in case of other document sources to on. Ensure the document (testbind.sxw) is not located in the pathlist. Open the document. Bug 1--> upon opening the document a warning dialog (#2 as defined in the security specs) should be launched it isn't. The warning dialog is launched when the user attempts to run the script. When the user selects run the script runs, when the user selects do not run the script does not run. Bug2 --> However it the user selects do not run, and subsequently attempts to run the script again, no warning dialog is displayed, the script does not run, the user must reload the document in order to get the warning dialog back. Bug 3--> Further, there is a check box in the warning dialog "Add this directory to the list of secure paths" If this checkbox is left unchecked, and the user selects run, the path is added to the list of secure paths.
changin target milestone
Open the document. Bug 1--> upon opening the document a warning dialog (#2 as defined in the security specs) should be launched it isn't. Problem is that we are not hooked into the document open in this release and cannot launch the warning dialog until the script is run. This needs to be release noted: requires_documentation. Other issues look like bugs. Assign to DF to fix. Bug 2: would expect the warning dialog to be redisplayed each time the script is invoked if they elect not to run. Bug 3: If checkbox is left unchecked surely the path should not be added.
Bug1: Exactly as per jmrice's comments. Bug2: Not a bug. Behaviour as per StarBasic. Bug3: Fixed! Precedence bug.
reopening issue
changing status to will fix later
The remain issues in the bug is now being tracked by issue 11727. Closing this issue.