Closed vick-subbu closed 5 years ago
Is there an easy way to change/override the position values when top='auto'; Any help would be really appreciated, this one use-case is having us blocked to go live
I'm able to reproduce this, I'll have some time to look at this today. It looks like the float: right is causing an issue here.
Is there any news on this one? This is also a blocker for us.
I'm getting this too.
Does anyone have a temp fix for this?
Having the same issue, and it's blocking our go live. Any temporary fix?
I'm closing this, this isn't an issue with tribute, but the way tribute is configured. Feel free to reopen if you have further issues or require further help!
I can verify this still is failing, even when using menuContainer
. If the number of menu items exceeds the bottom of the screen, it repositions the entire dropdown to the top of the page, and you have to scroll up to see it.
@dessalines please share your issue in a codepen or submit a failing test.
Ah, try making menuContainer
relative so that absolute elements can be positioned within it. Example: https://codepen.io/mrsweaters/pen/MWgGBvo
Still, would be nice to flip the list.
@mrsweaters I'm not sure if I'm doing something wrong but I can't get a menuContainer
with position: relative
to position the menu correctly if it is not the last element. Repro: https://codepen.io/aldhsu/pen/WNeWMxm.
My hunch is this code should not add the rect.top
or rect.left
if the menuContainer
is specified:
This probably needs to be documented as well. It seems unlikely that menuContainer
will work properly without position: relative
.
@mrsweaters I'm having the same issue. Even if the menuContainer position: relative
. I was able to make it work using this body {position: relative}
but i'm not sure it is the best solution. Can you tell me If there is a better one? Thank you!
@mrsweaters I'm having the same issue. Even if the menuContainer
position: relative
. I was able to make it work using thisbody {position: relative}
but i'm not sure it is the best solution. Can you tell me If there is a better one? Thank you!
yes @loicndjoyi this is the best solution
How can we reproduce this bug?
What did you expect to happen? I expect the menuContainer to be positioned closer to the input or contenteditable div What happened instead? It was positioned incorrectly as shown in the attached GIF
Link (jsfiddle/plunkr/codepen) or Screenshot: You can fork this Codepen as a base for reproducing your issue: https://codepen.io/mrsweaters/pen/OxxdWv?editors=1010#0