-
Notifications
You must be signed in to change notification settings - Fork 0
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
Etherscan charts do not get a button in Firefox #217
Comments
Postponing a sprint to give more time to charts, since it looks like this may be nontrivial. |
@hongyec indicates he has not been able to figure this out, so assigning to @jaydeepsingh25 for futher investigation or eventual reassignment. |
@hongyec in slack, you indicated (and showed screenshots) of the button appearing on etherscan.io charts. However, I just installed a newly built version of the firefox extension from main (built by Juliette), and using Firefox on Ubuntu Linux, I still do not see the buttons appearing. I am not sure if this is an OS-specific issue, or if there is some timing difference between your machine and mine, such that you see the buttons and I do not. |
Just verified the button does not appear when using it on my laptop (also running Ubuntu). Thought it might have different timing, so might work if that is the issue, but I'm 0/2 in this working on Ubuntu. |
@JRegimbal reports that it is not working for her on Debian either. She does see the charts button on the Quebec covid stats page, but not on etherscan.io. |
Testing firefox extension.
Ubuntu Linux, Firefox 99.0.1 (64-bit) installed via Snap.
Loaded extension manually, marked 0.2.4
Photos seem to work fine
Map on tutorial page seems to work fine
Charts on the quebec covid site seem to work same as in Chrome (https://www.quebec.ca/en/health/health-issues/a-z/2019-coronavirus/situation-coronavirus-in-quebec)
Go to etherscan:
https://etherscan.io/chart/tx
EXPECT: As in chrome, button appears underneath so can get rendering
ACTUAL: No button appears in Firefox.
Blocks public release of Firefox version of extension.
NOTE: @JRegimbal has experienced something similar (maybe identical), but can comment here if she has any more details.
The text was updated successfully, but these errors were encountered: