Closed felipeforte closed 4 years ago
The other ones are buttons that do in-page actions, that one is a link. I'd have to see a console.log for why it's not working, bc its working from Firefox and android right now.
I think it works if you click on the chain icon (the anchor element):
but won't work if you click on the green area (the button element excluding the chain icon):
Ah okay, I think I can alter this.
I think it works if you click on the chain icon (the anchor element):
but won't work if you click on the green area (the button element excluding the chain icon):
Both clicks have the same behavior. Or should I say the absence of behavior haha
The other ones are buttons that do in-page actions, that one is a link. I'd have to see a console.log for why it's not working, bc its working from Firefox and android right now.
How can I have access to the console.log to share with you?
Ah okay, I think I can alter this.
I tried to do the nesting in the reverse way (button inside the link) and it works, not sure if that’s the best practice. But seems like it’s not what this issue is about.
Both clicks have the same behavior. Or should I say the absence of behavior haha
Hmm, what happens if you click on the link in your picture?
Both clicks have the same behavior. Or should I say the absence of behavior haha
Hmm, what happens if you click on the link in your picture?
I mean, I don't know what you mean by "clicking". It's on the Inspector tool, so if I click on it, it just prompts me to edit the HTML code.
If I, however, copy and paste that link, it works.
Currently running on Parabola GNU/Linux-libre and GNU IceCat web browser.
The context button (the chain icon) is not functioning properly. While I do not have the technical expertise to pinpoint exactly why, I noticed something that might help:
This is the "Inspector" tool of GNU IceCat showing how the "context" button (highlighted) breaks the pattern of all other functioning buttons. Hope this helps!