Ulasan untuk Image Max URL
Image Max URL oleh qsniyg
4 ulasan
- Diberi peringkat 3 dari 5oleh JokeDeity, 2 tahun yang laluUsed to work great for me, but I'm back to googling everything because this doesn't return any different images anymore for me. Just shows the same image I'm searching from and never loads anything new. I never changed any of my settings, it just stopped working for me. Was really nice before it stopped. Can't find a setting that would change anything for the better.
Balasan pengembang
dikirim 2 tahun yang laluCould you let me know which websites don't work anymore? It's very possible they updated their websites in some way, and I haven't been aware of it to update it. Feel free to use any of the channels listed at the end of the addon's description for communication (github/discord/email etc.)
I also just updated the addon to 2023.8.0. See if it solves any of your issues :) - Diberi peringkat 3 dari 5oleh Pengguna Firefox 17568747, 2 tahun yang laluWorks great for the most part, but it breaks .mp4 files, converting them to .jpg in the browser. Ultimately had to remove this extension, and find a different one.
Balasan pengembang
dikirim 2 tahun yang laluIf you're referring to Imgur, this issue should be fixed in the next release: https://github.com/qsniyg/maxurl/issues/1050
If not, could you let me know which website it does this on? The issue you're describing is definitely not intended behavior, so I'd love to fix it if possible :) - Diberi peringkat 3 dari 5oleh Pengguna Firefox 14995623, 3 tahun yang laluDont working with instagram stories videos
- Diberi peringkat 3 dari 5oleh Burner, 5 tahun yang laluWhile it does work for the most part, the extension still feels like a userscript packaged into an extension. The biggest problem I regularly have is images loading in their entirety in a new tab before reloading the tab with the correct URL, which is... less than ideal.
Balasan pengembang
dikirim 5 tahun yang laluThanks for letting me know! 0.13.8 should be much faster for redirects now, as it's done on the extension side, rather than the content script :) The delay isn't entirely gone, as it still needs to perform a HEAD/GET request to ensure the larger image exists, but the userscript's overhead shouldn't be relevant for redirects now.
There's still more work to be done performance-wise, but I hope to be able to address some parts of them soon (others will require a rewrite of currently >55,000 lines of code, so, they will probably come a little less soon haha). I've tracked the issue here: https://github.com/qsniyg/maxurl/issues/294
Let me know if you have any other problems :)