«Market» not works in Steam

[piroJOKE]

A week ago, all was well. But now it was found that the «market» stops working on Steam's site, when it opens in Pale Moon.

If you try to "sell" items (card, etc) you see an empty panel of items and non-operating switches of categories of items.

In FF everything works without problems.

Can anyone help me with this problem?

[ron_1]

See if any of these will help. • clear your cookies; • try it in safe-mode; • try it in a new profile; • check "Firefox compatibility mode" (in Tools >> Options >> Advanced tab).

[piroJOKE]

I tried to log on from different computers, different Internet service providers, different Steam accounts.
No way...
"Compatibility " is also not helped.

[piroJOKE]

Im sorry for repeating, i have now new version of PM (25.8.0), but trade on market in Steam still NOT works.

http://steamcommunity.com/market/ ====> [Sell] button.

Empty inventory, unworkable buttons.

[Moonchild]

It seems to be a little iffy (then again, this is Steam we are talking about). It loads up more than what you show me on first load, but doesn't work 100%. I have to right-click on the frame, then choose frame->reload this frame, and then it all loads and works as-intended.

[half-moon]

Is this browser newly authenticated? If so, you need to wait 7 days.

[piroJOKE]

right-click on the frame, then choose frame->reload this frame, and then it all loads and works as-intended.

Confirm.

But how is it that in FF it works fine, bun in PM need «some magic»?

[Moonchild]

But how is it that in FF it works fine, bun in PM need «some magic»?

Pale Moon is not Firefox.

And why Steam doesn't want to send us everything on the first go is a good question. There's no real way for us to know why it gets hung up on their end. If you have time to experiment, then you can try and see if disabling HTTP pipelining (controlled by network.http.pipelining and network.http.pipelining.ssl) will help. If it does, then something on Steam's end (possibly a load balancer or reverse proxy) doesn't understand this part of the HTTP 1.1 standard very well and may need to be looked at by them.
Set both preferences to false and restart the browser.
I looked at SPDY as well as a possible culprit but I have that disabled myself by default, so that can't really be it if you have it on default settings.