-
Notifications
You must be signed in to change notification settings - Fork 196
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
why does webln.enable() return an object? #2596
Comments
Thanks for bringing this up. Since However that might break some existing applications out there 🤔 Did you notice any other services that use those parameters? |
i will do my best to hunt them down and help patch.. asking around here |
going through bolt.fun for LN enabled apps and compiling a list of patches for any apps that would break May need patchNo patch neededDoes not use webln.enable()
Uses webln.enable() properly |
cant find source code for Kollider browser extension... I checked kollider-lite-app and it seems unaffected by this tagging a few contributors maybe we can find out if @kolliderhq should patch too at least on the browser extension side... |
thank you @otech47. This is some old old thing (it got falsely added in the first commit even) |
According to this spec the enable function has a void return type
However the webln object injected by Alby has an enable function that does not adhere to this spec so it seems some app devs have assumed that enable may return an object with
enabled: true
orisEnabled: true
Seems this creates confusion for WebLN providers since
enable()
could be implemented in inconsistent waysCross-posting this in more than one place (BoltzExchange/boltz-web-app#229) since I'm not sure what the best approach to fix this is... implementations are either building on an outdated spec or they are not compliant with a spec that cannot be enforced 🤔
any suggestions on what to do here?
The text was updated successfully, but these errors were encountered: