that there is some blind assumption that $scope.strings exists; however, this is pretty logical as when I trace the relationship between hz-magic-search-bar to magic-search that it should always have something for the strings. horizon/static/framework/widgets/magic-search/hz-magic-search-bar.directive.js always sets a default (seemingly) and this is always passed via the associated template to the magic-search directive.
I do see another problem, which is that there is a hard-coded template path that may fail, in horizon/static/framework/widgets/magic-search/hz-magic-search-bar.html . I'll see if there's some correlation there.
I'm looking into this. First off, I can't recreate the issue.
I do notice in:
horizon/ static/ framework/ widgets/ magic-search/ magic-search. controller. js
that there is some blind assumption that $scope.strings exists; however, this is pretty logical as when I trace the relationship between hz-magic-search-bar to magic-search that it should always have something for the strings. horizon/ static/ framework/ widgets/ magic-search/ hz-magic- search- bar.directive. js always sets a default (seemingly) and this is always passed via the associated template to the magic-search directive.
I do see another problem, which is that there is a hard-coded template path that may fail, in horizon/ static/ framework/ widgets/ magic-search/ hz-magic- search- bar.html . I'll see if there's some correlation there.