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
Hello! I've been an avid user of GifCities for a while now, I really love the old web aesthetic and I'm glad there's a place where I can easily find these kind of gifs in one spot. I created a github account specifically to ask about the possibility of a pagination feature, as the infinite scroll function eventually causes my browser to hang after a while of scrolling through search results.
As I understand it, there's currently no active development on this right now and implementing a pagination feature is work in of itself. I've been deliberating on making a suggestion like this for a while now, as I'd really like to explore the full scope of Gifcities' collection without my browser being overwhelmed with too many graphics on the page. I also understand though that this is probably in the lower rungs of priorities for the developers, and as such might not be all that feasible. Either way I appreciate the consideration. 🙂
The text was updated successfully, but these errors were encountered:
Hello! I've been an avid user of GifCities for a while now, I really love the old web aesthetic and I'm glad there's a place where I can easily find these kind of gifs in one spot. I created a github account specifically to ask about the possibility of a pagination feature, as the infinite scroll function eventually causes my browser to hang after a while of scrolling through search results.
As I understand it, there's currently no active development on this right now and implementing a pagination feature is work in of itself. I've been deliberating on making a suggestion like this for a while now, as I'd really like to explore the full scope of Gifcities' collection without my browser being overwhelmed with too many graphics on the page. I also understand though that this is probably in the lower rungs of priorities for the developers, and as such might not be all that feasible. Either way I appreciate the consideration. 🙂
The text was updated successfully, but these errors were encountered: