Allright, that link works on PeakD.com and Keychain pops up.
I just tried to implement on one of my current wordpress projects and the link is gone - i think because it's not starting with a http/https or an #.
i wonder because keychain already added it's class "keychainify-checked" to the link ^.^ which it do everywhere where a link is when keychain is installed. cc @techcoderx cc @stoodkev
Edit: Just double-checked the Keychain Extension and found the keychainify section to tick the box to enable it. (but didnt solved the link issue on my WP Webpage (need to figure out why it doing this wierd stuff))
ok, found out how to get triggering it. and works on links! awesome - now i need more details about the keychainify feature, which is awesome and solving the problem actually.
Yep, and supported on peakd.com 😉
cc @louis88
Test link: 0.001 HIVE Transfer.
Allright, that link works on PeakD.com and Keychain pops up.
I just tried to implement on one of my current wordpress projects and the link is gone - i think because it's not starting with a http/https or an #.
i wonder because keychain already added it's class "keychainify-checked" to the link ^.^ which it do everywhere where a link is when keychain is installed. cc @techcoderx cc @stoodkev
Edit: Just double-checked the Keychain Extension and found the keychainify section to tick the box to enable it. (but didnt solved the link issue on my WP Webpage (need to figure out why it doing this wierd stuff))
ok, found out how to get triggering it. and works on links! awesome - now i need more details about the keychainify feature, which is awesome and solving the problem actually.
@stoodkev Bug-Found: It's allowing me to trigger a Popup, even when i have not activated the Keychainify Feature.
It's intended, Keychainify is for modifying HiveSigner links. Hive-URI is always active.
Ah, okay i understand. thx
Yes, most likely Wordpress is stripping it as a security feature. There's probably a way to add
hive://as an allowed URL scheme.