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

Initialize on a Specific Element #493

Open
jaydrogers opened this issue May 3, 2022 Discussed in #485 · 0 comments
Open

Initialize on a Specific Element #493

jaydrogers opened this issue May 3, 2022 Discussed in #485 · 0 comments
Labels

Comments

@jaydrogers
Copy link
Member

Discussed in #485

Originally posted by jaydrogers May 3, 2022

👉 Describe the problem

Currently AmplitudeJS binds to the entire page. This can be overkill and needs to be optional. Sometimes you only want to bind events to elements within a certain element.

👥 Problem evidence & reach

Any user who wants to narrow down and scope the binding of events to a certain element.
Specific Requests
#334
https://community.serversideup.net/t/multi-players-loadad-by-external-js/584/2

🥰 Describe the "impact" on users?

We can limit the scope of where AmplitudeJS is bound along with opening the door to making re-usable web components.

🏆 How to solve this problem

Allow the user to pass an element, identifier, etc. when initializing AmplitudeJS.

💯 How do we validate the problem is solved?

Users can bind AmplitudeJS events to a specific element and bind multiple times per page for multiple players.

@jaydrogers jaydrogers added the Enhancement ⚡️ New feature label May 3, 2022
@jaydrogers jaydrogers moved this to Being Documented in AmplitudeJS 6.0 May 3, 2022
@danpastori danpastori moved this from Being Documented to Ready for Development in AmplitudeJS 6.0 May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Ready for Development
Development

No branches or pull requests

1 participant