You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Spot.im comments initially load on Brave but show more, load more replies and Like button functionality does not work on aol.com
Platform (Win7, 8, 10? macOS? Linux distro?):
global
the issue is that spot.im as a third-party cannot access localStorage so it errors when the 'load more' button is clicked. changing to 'allow all cookies' fixes the issue
The linked to page in the issue no longer demonstrates the issue in any browser since the chat widget has been removed. So I think the issue should be closed, or at the least, some new site found that demonstrates the problem
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Spot.im comments initially load on Brave but show more, load more replies and Like button functionality does not work on aol.com
Platform (Win7, 8, 10? macOS? Linux distro?):
global
Brave Version (revision SHA):
36ae2ec
Steps to reproduce:
Actual result:
Highlighted buttons on Windows are not functional.
Same result on macOS:
Expected result:
Spot.im comment features function properly, expanding when needed and allowing for engagement.
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes.
Is this an issue in the currently released version?
Yes.
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Note this is probably something similar to what we encounter with Disqus, when ad features are enabled by the publisher.
We should:
The text was updated successfully, but these errors were encountered: