EDITED:
Here's how it works (the still long and exhaustive explanation):
- Create a custom directive that allows you to target the trigger element.
- Create a custom directive that is added to the body and will find the trigger element and fire the custom event when it is clicked.
Create a custom directive to target the trigger element:
You need to trigger the custom event handler from the element that opened the popover (in the demo this is the button). The challenge is that the popover is appended as a sibling to this element and I always think that things have greater potential to break when you are traversing the DOM and expecting it to have a specific structure. There are several ways you can target the trigger element, but my approach is to add a unique classname to the element (I choose 'trigger') when you click on it. Only one popover can be opened at a time in this scenario, so it's safe to use a classname, but you can modify to suit your preference.
Custom Directive
app.directive('popoverElem', function(){
return{
link: function(scope, element, attrs) {
element.on('click', function(){
element.addClass('trigger');
});
}
}
});
Applied to button
<button popover-template="dynamicPopover.templateUrl" popover-title="{{dynamicPopover.title}}" class="btn btn-default" popover-elem>Popover With Template</button>
Create a custom directive for the document body (or any other element) to trigger the popover close:
The last piece is to create a custom directive that will locate the triggering element and fire the custom event to close the popover when the element it is applied to is clicked. Of course, you have to exclude the initial click event from the 'trigger' element, and any elements you want to interact with on the inside of your popover. Therefore, I added an attribute called exclude-class so you can define a class that you can add to elements whose click events should be ignored (not causing the popover to close).
To clean things up, when the event handler is triggered, we remove the trigger class that was added to the trigger element.
app.directive('popoverClose', function($timeout){
return{
scope: {
excludeClass: '@'
},
link: function(scope, element, attrs) {
var trigger = document.getElementsByClassName('trigger');
function closeTrigger(i) {
$timeout(function(){
angular.element(trigger[0]).triggerHandler('click').removeClass('trigger');
});
}
element.on('click', function(event){
var etarget = angular.element(event.target);
var tlength = trigger.length;
if(!etarget.hasClass('trigger') && !etarget.hasClass(scope.excludeClass)) {
for(var i=0; i<tlength; i++) {
closeTrigger(i)
}
}
});
}
};
});
I added this to the body tag so that the entire page* acts as a dismissible backdrop for the popover:
<body popover-close exclude-class="exclude">
And, I added the exclude class to the input in the popover:
<input type="text" ng-model="dynamicPopover.title" class="form-control exclude">
So, there are some tweaks and gotchas, but I'll leave that to you:
- You should set a default exclude class in the link function of the popover-close directive, in case one is not defined.
- You need to be aware that the popover-close directive is element bound, so if you remove the styles I set on the html and body elements to give them 100% height, you could have 'dead areas' within your viewport if your content doesn't fill it.
Tested in Chrome, Firefox and Safari.
