Skip to content
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

Can't open images #2240

Closed
mattnoir opened this issue Nov 16, 2024 · 4 comments
Closed

Can't open images #2240

mattnoir opened this issue Nov 16, 2024 · 4 comments

Comments

@mattnoir
Copy link

Seems like messenger changed something again and I am not able to open pictures in messages, nothing happens when I click on it.

Also, seems like Caprine is done, last modification 7 months ago, hundreds of issues open, several pull requests open as well. Is there some client that works in a similar way and is not abandoned? Thanks

@carneeki
Copy link

+1 - I first noticed images would not open two or three days ago, I thought it was just me.

@SilverSaw
Copy link

SilverSaw commented Nov 18, 2024

This is due to hide-preferences-window bug, a workaround is listed here #2167 , but since 2 days caprine has been forcing hide-preferences-window automatically on every restart. We are unable to manually change this permanently, and the bug is critical, on every restart we have to remove it manually to make caprine work.

@thankarezos
Copy link

This is due to hide-preferences-window bug, a workaround is listed here #2167 , but since 2 days caprine has been forcing hide-preferences-window automatically on every restart. We are unable to manually change this permanently, and the bug is critical, on every restart we have to remove it manually to make caprine work.

I found a workaround for that too. Go to file>caprine settings > advanced > custom styles and put this.

html.hide-preferences-window div[class='x9f619 x1n2onr6 x1ja2u2z'] > div:nth-of-type(3) > div > div {
    display: block !important;
}

This should nullify it.

@mquevill
Copy link
Collaborator

mquevill commented Dec 1, 2024

This should be fixed as of v2.60.3. If you're still having this issue with that version, feel free to reopen this issue.

@mquevill mquevill closed this as completed Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants