-
Notifications
You must be signed in to change notification settings - Fork 32
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
Download button not working when post/reel was opened in new tab #36
Comments
Same issue here as well, setting url in the download button and opening it directly in new tab ends up showing the profile icon image instead of the post image. Home feed works amazing, but half the time I have to manually fetch image url from source if it's in a new tab. |
It looks like this: #35 right? I am using Firefox, I think there is a problem with the IG website. If the buttons are at the top, I can't reply to messages sometimes. (When I click 'view replies' it drops open, then immediately collapses again) |
i am having the same problem. When I open it in a new tab, the download button does not appear. (firefox 114.0.1) |
Can you try again with 1.17.3 or 1.17.4? (may need to download from greasyfork) |
I already downloaded it from greasyfork. It doesn't work at all in version 1.17.4. so I reverted to version 1.17.3. In version 1.17.3, although the download buttons do not appear in the new tab, at least they appear on the normal page. |
Hi there!
To clarify, your userscript works phenomenal, when I open a post from grid view (i.e. the user's profile page). In that case the download button is on the bottom of the overlay, next to the save button.
What does, at least for me, not work is when I open a post in a new tab or get there from a direct link (e.g. https://www.instagram.com/p/CsJv4hNJzdb/). In that case, the download button appears on the top next to the user's handle. Clicking it will do nothing.
Same applies to reels. Anytime the download button is on top, it just does nothing. When it's on the bottom it works like a charm. That's why I assume, the bug lies somewhere in the code responsible for the placement next to the Instagram handle.
(I'd personally prefer if the button is consistently at the bottom anyway, but that's just as side note.)
Tested with script version 1.16.1 and 1.16.2 in Google Chrome 113 using Tampermonkey.
Hope that helps,
kind regards!
The text was updated successfully, but these errors were encountered: