Actual Behavior:
What is the issue? * md-tooltips in 1.1.3 do not appear in the correct position when the md-direction attribute is changed, after rolling over the tooltip at least once. It appears the edge of the tooltip being used to calculate the position is determined on first roll-over of the tooltip, and not updated if the direction is changed.What is the expected behavior? Tooltips should position themselves as they did in version 1.1.1.CodePen (or steps to reproduce the issue): *
CodePen Demo which shows your issue: http://codepen.io/anon/pen/qRvEGwDetails: Roll over the FAB with the radio set to "bottom", then switch the direction radio button to "left". The _top_ of the tooltip is aligned with the center of the FAB instead of the center of the right edge being aligned to the center of the FAB, as expected.Angular Versions: *
Angular Version: 1.5.5Angular Material Version: 1.1.3Additional Information:
Browser Type: * ChromeBrowser Version: * 55.0.2883.87OS: * Windows 7Stack Traces:Shortcut to create a new CodePen Demo.
Note: * indicates required information. Without this information, your issue may be auto-closed.
Do not modify the titles or questions. Simply add your responses to the ends of the questions.
Add more lines if needed.
I experience this too when html dir is set to rtl.
this is mdPanel position -related issue.
js does'nt assign 'left' as it does when dir attr is set to ltr.
+1
+1
+1
Ok so we ended up building our own.
It seems to me like tooltip positioning is completely unreliable once you put multiple tooltips on the same page. We see completely misaligned tooltips on successive hover actions without changing direction.
Seems like our issue is actually #10543
hi @eqbalsajadi ,
its seems like the problem is in the _reverseXPosition() - when the position is center its return undef and that cause the tooltip to be position wrongly.
in this case this function should return the position
MdPanelPosition.prototype._reverseXPosition = function(position) {
if (position === MdPanelPosition.xPosition.CENTER) {
return;
}
var start = 'start';
var end = 'end';
proposed solution:
MdPanelPosition.prototype._reverseXPosition = function(position) {
if (position === MdPanelPosition.xPosition.CENTER) {
return position;
}
var start = 'start';
var end = 'end';
@eladh hi,
I'm moving to material2 right now
hope to not have such probs in material2
hope to not have such probs in material2
@oliversalzburg Thanks
Are we seeing this bug taken into consideration?
Verified in this CodePen that this was not fixed by the changes in https://github.com/angular/material/pull/10651.
We're currently in need of a PR being submitted that fixes this issue.
I think I know why this happens. Working on a fix.
Most helpful comment
Angular Version: 1.6.2
Angular Material Version: 1.1.3