From 042ad8e27154fdb7796295be27f0f4e007a0b751 Mon Sep 17 00:00:00 2001 From: Adam Bradley Date: Mon, 10 Feb 2014 11:20:42 -0600 Subject: [PATCH] feature(DOM): Experiment w/ excluding 'ng-scope' and 'ng-isolate-scope' classnames from elements MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ultimate goal is to reduce DOM manipulations. It appears 'ng-scope' and 'ng-isolate-scope' classnames are not required for Angular to work. So in an effort to reduce any DOM manipulations, we’re going to try to excluding them from being added to elements and see what comes of it. --- .../angular/src/service/angularOverrides.js | 2 +- js/ext/angular/test/dom-trace.js | 25 ++----------------- 2 files changed, 3 insertions(+), 24 deletions(-) diff --git a/js/ext/angular/src/service/angularOverrides.js b/js/ext/angular/src/service/angularOverrides.js index 01daa9ba06..0e9ef4819b 100644 --- a/js/ext/angular/src/service/angularOverrides.js +++ b/js/ext/angular/src/service/angularOverrides.js @@ -1,7 +1,7 @@ angular.element.prototype.addClass = function(cssClasses) { var x, y, cssClass, el, splitClasses, existingClasses; - if (cssClasses) { + if (cssClasses && cssClasses != 'ng-scope' && cssClasses != 'ng-isolate-scope') { for(x=0; x