fng-bootstrap-datetime 0.12.0-beta.193 → 0.12.0-beta.195
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -173,13 +173,14 @@ angular.module('ui.bootstrap.datetimepicker', ["ui.bootstrap.dateparser", "ui.bo
|
|
173
173
|
// ****************************************************
|
174
174
|
// HACK RIGHT HERE!
|
175
175
|
// For cases where formsAngular.elemSecurityFuncBinding is set to either "one-time" or "normal", the
|
176
|
-
// result of the call to handleReadOnlyDisabled() made by the fngUiBootstrapDatetimePicker directive
|
177
|
-
// include reference(s) to
|
178
|
-
//
|
179
|
-
//
|
180
|
-
if (formsAngular.
|
181
|
-
$scope
|
182
|
-
|
176
|
+
// result of the call to handleReadOnlyDisabled() made by the fngUiBootstrapDatetimePicker directive might
|
177
|
+
// include reference(s) to two functions which our ancestor form scope should have been decorated with -
|
178
|
+
// isSecurelyDisabled and requiresDisabledChildren. Because our scope is isolated, these will be
|
179
|
+
// inaccessible to us unless we do the following...:
|
180
|
+
if (formsAngular.disabledSecurityFuncName) {
|
181
|
+
$scope.isSecurelyDisabled = $scope.$parent.isSecurelyDisabled;
|
182
|
+
$scope.requiresDisabledChildren = $scope.$parent.requiresDisabledChildren;
|
183
|
+
}
|
183
184
|
// as this is only going to work for disabled state arising from fng security, and not the case
|
184
185
|
// where an fng field has a string-valued readonly attribute that refers to a function on the parent
|
185
186
|
// scope, it's only a partial solution. the general solution would presumably be to replace our isolated
|