unable to change page with the CSfloat extension

[aquibbaig]

I'm unable to go to next pages in the steam community market while having the extension ON. It works as expected when turning the extension OFF.

-- details
browser: Google Chrome Version 134.0.6998.118 (Official Build) (arm64)

Screen.Recording.2025-03-24.at.8.46.31.AM.mov

[Step7750]

Typically this is due to being rate limited on Steam (or Steam just being slow).

Did you change your page size in the extension?

What version of the extension do you have?

I'm not able to reproduce this locally, which makes me think you're just getting rate limited by Steam.

[Kryptlock]

Typically this is due to being rate limited on Steam (or Steam just being slow).

You are correct!

Rate limiting is indeed usually the cause.
I my I've even seen it happen in real time confirmed as I had been monitoring events through Chromes "developer tool"
It happened during first time I used the extension while browsing the steam marketplace a few hours ago,
Well.. I learned my lesson fairly quick with that one.
(or did I? 🤔 I mean... I made it 47 pages deep before I got limited! that's not bad if you as me)

 

However, there may be an issue that elsewhere as well.

The extension had crashed for me as well It occurred While choosing a "filter color" during the process of setting up my first one ever about a half hour or so ago.

Also,I know for sure I was not rate limited as I had just loaded the page Without making any calls anywhere on steam for probably about 10 minutes after learning my prior lesson haha.
I even confirmed in chrome dev tools open On my secondary monitor at the time.

 
Regardless, Sorry, getting back on track lol, like I said at some point while dragging around the eyedropper to choose a custom color, the page the page froze.

I realized it was likely due to the extension as that was the currently being actively utilized And was only recently changed variable in the environment and I never had such issues ever prior.

So I decided to open up the home extensions manager and I noticed that it said the service worker was turned off, and it also had stated that the app had crashed.

 
Coincidentally, probably 10 minutes prior to this event, I had enabled The option to collect errors.
I had to wake up the service worker manually because it didn't start for some reason

Anyway, after the crash, returning to the Extension management page for the new issue; I then clicked the button to give more info which brought me to a little "window pane/View field" on a separate page.

It had contained a little snippet of some code that appeared to print a response of which I assume was supposed to be response pointing to a custom defined reason for the crash.
But Unfortunately.. the bad news is I deleted it..

 
But in my defense, and maybe to provide some reprieve:
I deleted it because from the little digging I did do, it appeared the reason returned wasn't defined anyway.

I apologize for deleting it and not being able to give anymore context I wasn't expecting literally randomly stumble upon this post less than an hour later..

Edit:(4? Fk STT) Again, Added some missing literary context, as well as fixed a few formatting inaccuracies.