Component and Directive selector property doesn't actually restrict by element tag or attribute

Title is pretty self explanatory, so here’s an example:

@Directive({ selector: '[some-directive]' })
export class MyDirective {
  constructor(@Inject('$element') $element) {
    console.log($element);
  }
}

This directive will log the creation of a controller on both <some-directive></some-directive> and <div some-directive></div> event though the query selector specified should only match attribute values. This happens vice versa for directives made with @Component.

I’m assuming this is not intended behavior and I’m not expected to inlcude legacy: { restrict: 'A' } in all my directive definitions.

[kherock]

Haha yes, true. I actually only discovered it by accident when trying to port over ng-forward’s DOM event directives to my project when the 'input' directive started behaving strange (matching <input> elements). And then that’s where I ran into #129 😛

Anyway, I gave up on that and just switched everything back to ng-${event}.

[kherock]

Can we have it so that the selector provided is actually mapped to a restriction? A case that I need is a directive on all <video> elements to do something when the loadedmetadata event fires. The selector I should use in this case would be 'video', not '[video]', but it won’t work if use @Directive. Angular 2 supports this use.

Using legacy: { restrict: 'E' }, works around the issue, but the change in 2.2.0 was actually breaking for me.