Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix tooltip positioning for IE8 broken in 2.3.0 #6737

Merged
merged 1 commit into from
Feb 6, 2013

Conversation

gsmet
Copy link
Contributor

@gsmet gsmet commented Jan 29, 2013

IE8 defines a broken placeholder object getBoundingClientRect which breaks the new getPosition() method introduced in 2.3.0

As height and width are not defined in the getPosition() result, tooltips aren't positioned correctly.

This pull request fixes #6659 .

IE8 defines a placeholder object getBoundingClientRect which breaks the new getPosition() method
@craue
Copy link

craue commented Feb 4, 2013

👍

fat added a commit that referenced this pull request Feb 6, 2013
…or-ie8

Fix tooltip positioning for IE8 broken in 2.3.0
@fat fat merged commit 31b9240 into twbs:2.3.0-wip Feb 6, 2013
@fat
Copy link
Member

fat commented Feb 6, 2013

rad dude, thanks!

@vadimk
Copy link

vadimk commented Feb 8, 2013

Tooltip positioning now doesn't work at all http://twitter.github.com/bootstrap/javascript.html#tooltips with 2.3.0

@craue
Copy link

craue commented Feb 8, 2013

Indeed the data-placement attribute seems to be ignored.

@craue
Copy link

craue commented Feb 8, 2013

See #6832.

@gsmet
Copy link
Contributor Author

gsmet commented Feb 8, 2013

The regression isn't due to my pull request. It works like a charm with data-placement as we are using it.

I think the regression is most likely related to this patch: 1fe4ed8#js/bootstrap-tooltip.js .

The version we use here at work only has this commit missing and data-placement works flawlessly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants