Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(377)

Unified Diff: third_party/pkg/angular/lib/directive/ng_src_boolean.dart

Issue 1058283006: Update pubspecs and dependencies to get pkgbuild tests working. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 5 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/pkg/angular/lib/directive/ng_src_boolean.dart
diff --git a/third_party/pkg/angular/lib/directive/ng_src_boolean.dart b/third_party/pkg/angular/lib/directive/ng_src_boolean.dart
deleted file mode 100644
index f2d57ead6a303c3381561ec1a615fd734ae5128e..0000000000000000000000000000000000000000
--- a/third_party/pkg/angular/lib/directive/ng_src_boolean.dart
+++ /dev/null
@@ -1,106 +0,0 @@
-part of angular.directive;
-
-/**
- * Allows adding and removing the boolean attributes from the element.
- *
- * Using `<button disabled="{{false}}">` does not work since it would result
- * in `<button disabled="false">` rather than `<button>`.
- * Browsers change behavior based on presence/absence of attribute rather the
- * its value.
- *
- * For this reason we provide alternate `ng-`attribute directives to
- * add/remove boolean attributes such as `<button ng-disabled="{{false}}">`
- * which will result in proper removal of the attribute.
- *
- * The full list of supported attributes are:
- *
- * - [ng-checked]
- * - [ng-disabled]
- * - [ng-multiple]
- * - [ng-open]
- * - [ng-readonly]
- * - [ng-required]
- * - [ng-selected]
- */
-@NgDirective(selector: '[ng-checked]', map: const {'ng-checked': '=>checked'})
-@NgDirective(selector: '[ng-disabled]', map: const {'ng-disabled': '=>disabled'})
-@NgDirective(selector: '[ng-multiple]', map: const {'ng-multiple': '=>multiple'})
-@NgDirective(selector: '[ng-open]', map: const {'ng-open': '=>open'})
-@NgDirective(selector: '[ng-readonly]', map: const {'ng-readonly': '=>readonly'})
-@NgDirective(selector: '[ng-required]', map: const {'ng-required': '=>required'})
-@NgDirective(selector: '[ng-selected]', map: const {'ng-selected': '=>selected'})
-class NgBooleanAttributeDirective {
- final NodeAttrs attrs;
- NgBooleanAttributeDirective(this.attrs);
-
- _setBooleanAttribute(name, value) => attrs[name] = (toBool(value) ? '' : null);
-
- set checked(value) => _setBooleanAttribute('checked', value);
- set disabled(value) => _setBooleanAttribute('disabled', value);
- set multiple(value) => _setBooleanAttribute('multiple', value);
- set open(value) => _setBooleanAttribute('open', value);
- set readonly(value) => _setBooleanAttribute('readonly', value);
- set required(value) => _setBooleanAttribute('required', value);
- set selected(value) => _setBooleanAttribute('selected', value);
-}
-
-/**
- * In browser some attributes have network side-effect. If the attribute
- * has `{{interpolation}}` in it it may cause browser to fetch bogus URLs.
- *
- * Example: In `<img src="{{username}}.png">` the browser will fetch the image
- * `http://server/{{username}}.png` before Angular has a chance to replace the
- * attribute with data-bound url.
- *
- * For this reason we provide `ng-`prefixed attributes which avoid the issues
- * mentioned above as in this example: `<img ng-src="{{username}}.png">`.
- *
- * The full list of supported attributes are:
- *
- * - [ng-href]
- * - [ng-src]
- * - [ng-srcset]
- */
-@NgDirective(selector: '[ng-href]', map: const {'ng-href': '@href'})
-@NgDirective(selector: '[ng-src]', map: const {'ng-src': '@src'})
-@NgDirective(selector: '[ng-srcset]', map: const {'ng-srcset': '@srcset'})
-class NgSourceDirective {
- final NodeAttrs attrs;
- NgSourceDirective(this.attrs);
-
- set href(value) => attrs['href'] = value;
- set src(value) => attrs['src'] = value;
- set srcset(value) => attrs['srcset'] = value;
-
-}
-
-/**
- * In SVG some attributes have a specific syntax. Placing `{{interpolation}}` in
- * those attributes will break the attribute syntax, and browser will clear the
- * attribute.
- *
- * The `ng-attr-*` is a generic way to use interpolation without breaking the
- * attribute syntax validator. The `ng-attr-` part get stripped.
- *
- * @example
- * <svg>
- * <circle ng-attr-cx="{{cx}}"></circle>
- * </svg>
- */
-@NgDirective(selector: '[ng-attr-*]')
-class NgAttributeDirective implements NgAttachAware {
- final NodeAttrs _attrs;
-
- NgAttributeDirective(this._attrs);
-
- void attach() {
- String ngAttrPrefix = 'ng-attr-';
- _attrs.forEach((key, value) {
- if (key.startsWith(ngAttrPrefix)) {
- var newKey = key.substring(ngAttrPrefix.length);
- _attrs[newKey] = value;
- _attrs.observe(key, (newValue) => _attrs[newKey] = newValue );
- }
- });
- }
-}
« no previous file with comments | « third_party/pkg/angular/lib/directive/ng_show_hide.dart ('k') | third_party/pkg/angular/lib/directive/ng_style.dart » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698