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

Feature Discovery needs better documentation #252

Open
nh916 opened this issue Feb 28, 2022 · 4 comments
Open

Feature Discovery needs better documentation #252

nh916 opened this issue Feb 28, 2022 · 4 comments

Comments

@nh916
Copy link

nh916 commented Feb 28, 2022

I have been having a very hard time figuring out how to use the feature discovery and how to chain multiple of them together to make a walkthrough.

I really wish we had better examples that were full and showed how to use it. For example, I kept doing instances.open( ) and kept getting "method does not exist" error, after an hour of debugging I found out that its instances[0].open( ). I think our documentation could use some improvement to make it simpler for any of us to understand.

Here is the gist that I am currently struggling with to create a walkthrough for a new user
https://gist.github.com/nh916/b2a7512fbe9b4d24de8c5f909a7c6053

@nh916
Copy link
Author

nh916 commented Mar 4, 2022

Also it seems to only work when the element is set as display: inline; and not anything else

@jshster
Copy link

jshster commented Jun 2, 2022

Hi there, improving the documentation is one of the top priorities of the project maintainers. I myself have had some huge issues trying to understand how to implement some of the features (date picker mainly). I will add it to the maintainers discussions.

@nh916
Copy link
Author

nh916 commented Jun 3, 2022

Worst case scenario under some of the more problematic ones we can add a link to a working codepen as a demo for someone to build off of

@ivanBell199
Copy link

ivanBell199 commented Dec 14, 2022

Hello! Perhaps you already solved the issues you were facing. But I'd like to post here that the "menu" element needs position: relative. Then the tap-target area will be positioned correctly. However I noticed that when the menu element is somewhere in center of the page, the text is often positioned not so well. But maybe it's just my taste :) Please see the image:
image

You can also check out my codepen: https://codepen.io/iBeliakov/pen/Yzvogoa

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

No branches or pull requests

3 participants