-
Notifications
You must be signed in to change notification settings - Fork 975
Pocket extension on Windows ia32 is always red #7357
Comments
was this fixed with #7437? |
@srirambv @alexwykoff can we retest this one? if it's still an issue, maybe we can push to 0.14.3. Thanks 😄 |
Moving to 0.14.3 |
This is expected behavior. We shouldn't show a red pocket. |
I think it is somewhat confusing... since other icons around the pocket one change color based on status. LastPass changes the color into yellow when the extension has a warning notification. Shield button changes its color too. I don't see the reason to disable color change on Pocket. |
@luixxiul do you have a way to test in Chrome using a 32 bit Windows VM? I am curious if Chrome has the same issue |
ok I'll give a try. |
The pocket icon seems to have the color based on the status. See: #9157 (comment). @srirambv would you check the icon again with a fresh profile? if it is confirmed that the bug has been fixed, please re-close the issue. Thanks! |
Doesn't seem to be an issue for Windows ia32. Pocket icon becomes grey when navigated to a unmarked page and shows red when opened Closing the issue for now cc: @luixxiul |
confirmed pocket icon is not always red on MacOS after pocket is enabled. however, cannot confirm it becomes red due to #9669 |
Test plan
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Pocket extension on Windows i32 is always red
Platform (Win7, 8, 10? macOS? Linux distro?):
Windows 7 ia32
Brave Version (revision SHA):
Brave 0.13.4
rev 71d8ffc
Steps to reproduce:
Actual result:
Shows red icon after enabled
Expected result:
Should not show the red icon, should show red icon only when a page is saved
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?
No
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
The text was updated successfully, but these errors were encountered: