@@ -967,7 +967,6 @@ function $CompileProvider($provide, $$sanitizeUriProvider) {
967
967
* See {@link ng.$compile#-bindtocontroller- `bindToController`}.
968
968
* - `transclude` – `{boolean=}` – whether {@link $compile#transclusion content transclusion} is enabled.
969
969
* Disabled by default.
970
- * - `isolate` – `{boolean=}` – whether the new scope is isolated. Isolated by default.
971
970
* - `restrict` - `{string=}` - a string containing one or more characters from {@link ng.$compile#-restrict- EACM},
972
971
* which restricts the component to specific directive declaration style. If omitted, this defaults to 'E'.
973
972
* - `$canActivate` – `{function()=}` – TBD.
@@ -982,7 +981,7 @@ function $CompileProvider($provide, $$sanitizeUriProvider) {
982
981
* directives. Component definitions usually consist only of a template and a controller backing it.
983
982
*
984
983
* In order to make the definition easier, components enforce best practices like use of `controllerAs`,
985
- * `bindToController` and default behaviors like **isolate scope** and restriction to elements.
984
+ * `bindToController`, **isolate scope** and default behaviors like restriction to elements.
986
985
*
987
986
* Here are a few examples of how you would usually define components:
988
987
*
@@ -1071,7 +1070,7 @@ function $CompileProvider($provide, $$sanitizeUriProvider) {
1071
1070
template : makeInjectable ( template ) ,
1072
1071
templateUrl : makeInjectable ( options . templateUrl ) ,
1073
1072
transclude : options . transclude ,
1074
- scope : options . isolate === false ? true : { } ,
1073
+ scope : { } ,
1075
1074
bindToController : options . bindings || { } ,
1076
1075
restrict : options . restrict || 'E'
1077
1076
} ;
0 commit comments