Add a Constant Class to Popup/Hover Menus
### Problem Statement
There is currently no way to easily access popup divs programmatically. You can access them through complex css selectors, but if the DOM ever changes then the selectors will have to be redone.
### Use Case
When creating extensions for workflowy it is useful to be able to access the popups because they're the perfect place to add extra functionality. If you want to add any sort of button that requires information about a bullet, the popup is the obvious place to put it.
I think it could also be useful for people using extensions to reskin workflowy, although I haven't done this personally.
### Suggestion
For the project I am currently working on the optimal solution would be two constant css classes:
- One class for the menu that appears when you hover on a bullet.
- Another for the menu that appears when you click the more options button.
The reason for the separate classes is that the more options popup has different functionality if it is attached to the top-level (invisible) bullet.
### Additional Information
If I remember correctly your current setup removes all of the classes on a popup to replace them with your hashed selector class. I think it would be useful to instead just remove the old hashed class and leave any constant/extension-added classes. But I could be completely misunderstanding your backend hehe.
### Thank you!
This post probably incorrectly assumes some things about how Workflowy works, so I appologize for any misunderstanding. I know this is probably harder to impliment than it seems to an outsider, and may only useful for me hehe but I appreciate you reading it anyway! Thank you so much for creating a great tool!
-
A big +1 for this request.
I would add the following. Consider adding official API methods for adding to the hover menu, the toolbar, and the multi-select menu. This way WorkFlowy could maintain it's minimalist Zen, and devs/users could opt make things "less minimal" with extensions.
Please sign in to leave a comment.
Comments
1 comment