-
Notifications
You must be signed in to change notification settings - Fork 6.7k
more tooltip issues #132
Comments
@Skivvies - Thanks for reporting. I updated the issue to include the specific issues from your plunker. For issue 1, the reason is that btn-group's styling is based on the last child and when the tooltip is visibile, it becomes the last child instead of the button. This issue is present in the jQuery version too: http://plnkr.co/edit/3ERe0roEG6683QyT3qVy?p=preview. I'm not sure how to cleanly fix this. For issue two, this is due to scoping and is not an issue. Because the tooltip has a child scope, any other directives we use are in the child scope that inherits prototypically from the parent. Primitive values are copies and not references, so when the ngClick is referencing the Does anyone have ideas for resolving the first one? The only solution would be to move the inserted tooltip to someplace else in the DOM, but no matter where it goes, it could cause the same issue. |
Thanks for the quick reply @joshdmiller. Did you see the tooltip improvements in http://blog.getbootstrap.com/2013/02/07/bootstrap-2-3-released/? Is the new |
@Skivvies I added the wrapping as the third issue. I'll have to look at that in more detail. The container option is related, I suppose. Prior to 2.3 (and therefore on what we based this) the tooltip node was simply inserted directly after the element on which it was defined. v2.3 added the option to specify where it gets inserted. That wouldn't solve this, per se, but it would provide special-case workarounds. The problem is there isn't a good way to do that in AngularJS; throwing around DOM nodes mixes concerns awkwardly. I'll put some more thought into tha too. But if anyone else has ideas, feel free to jump in... |
Maybe not a long-term solution, but for now tooltip could just take a boolean option for whether to use insertAfter or to append to the body, which is how tooltips worked prior to Bootstrap 2.2.2, and which would give people experiencing the issues in this ticket a workaround. What do you think? |
@joshdmiller I just sketched something out in skivvies/bootstrap@d33bc6f which allows you to pass in a selector to a new |
Hey @joshdmiller, did you happen to get any ideas about the wrapping issue? I'm trying to figure out what's going on and not having any luck. |
@Skivvies AFAIK wrapping the original bootstrap version is done by allowing Having said this I'm more and more thinking of adding the $sanitize service so some markup would be allowed. |
OK, we've started discussing several issues here but in the end we've got 2 things to tackle:
Going to close this one so we've small, focused issues to tackle. |
Call function onSelect
Two issues:
See http://plnkr.co/edit/QVTAoP
The text was updated successfully, but these errors were encountered: