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
new syncer: New save dropdown is partially hidden #4531
Comments
Hi @pmario this is the same issue we have with the adjacent "more" dropdown, it's not specific to the new syncer fixes. |
@Jermolene |
Yea, cool. The default dropdown should be fixed too. |
"more" dropdown is still readable, but with the syncer text gets cut off. |
The problem is exacerbated because the prerelease has fluid-fixed layout with a relatively narrow sidebar. |
see: https://groups.google.com/g/tiddlywiki/c/dFxN3eIrAzo/m/6h9rISmTDAAJ |
also see: #4393 |
Thank you @pmario. I hope @Jermolene have a look at this old issue! As you said the Repopup addresses this issue partially! I think we can use reveal widget also for tooltip! In Refnotes plugin I use tooltip to show footnotes and citations. The issue is with mobile browser when users experience off screen tooltip. There is no way in Tiddlywiki to reposition them and address the offscreen issue! ping @TiddlyTweeter |
Tx @kookma for the ping! Somehow floating back into view dropdowns in general in TW would be a real PLUS on usability. Especially on smart phone. I personally like the entire tag system in TW. It is great for making menus quickly and very easily. |
Some thoughts, although I expect others have more knowledge of this and there are standard ways to address this. I have wondered if there were a way to set centre or right align such popups, I could imagine centre being popular on mobile screens but as long as we can still relate the popup to the original trigger, especially if it needed click/touch to close. I imagine if the starting point is left or right of centre then from this the direction to open could be determined. Tony |
It is like this:
IMO it should be like this: with
position="belowleft"
-- which is a little bit better.The text was updated successfully, but these errors were encountered: