Angular will definitely apply directives in <head>, unless you’re
bootstrapping the application (with ng-app) somewhere other than <html>,
such as <body>.
But if Angular is able to interpolate expressions and ng-repeat, then it
should be able to use your custom directive. Something is likely off in the
directive definition.
On Friday, October 3, 2014 8:12:52 AM UTC-7, Joberto Diniz wrote:
>
> I have the following in *<head>* of html:
>
> *<meta name="{{meta.name <http://meta.name>}}"
> property="{{meta.property}}" content="{{meta.content}}" ng-repeat="meta in
> metas" />*
>
> *metas* is an array that is added to *$rootScope*. However, there are
> meta tags which require *name* and other which require *property*, but
> not both. So, the way it is implemented, some *name* ou *property* will
> be empty, and that is a problem.
>
> I thought of creating a directive *<meta-tags>* but it seems angular
> doesn't parse it in *<head>* section. Any ideas?
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
