ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.25k stars 175 forks source link

Steam Client for Linux can no longer purchase games in Big Picture Mode - Yikes!! #5896

Open m9115m opened 6 years ago

m9115m commented 6 years ago

My System logs are attached to Steam Ticket# HT-BR6V-Y4QH-3P9Y

D'oh!! With the latest release of Steam Client for Linux, you can not longer purchase games in Big Picture Mode.

Yikes

The screens appear to have an issue showing the Shopping Cart, as the pricing never appears. After the game is listed, payment info is collected, but the transaction doesn't complete. Instead, you enter credit card info, then billing address, then hitting complete, the app stays on same page, and doesn't show the final approval page.

I checked in Non Big Picture mode and payment processing works as usual.

Whoops!!

Thanks

Steps for reproducing this issue:

1.With the Linux Client, try purchasing a game in Big Picture Mode

kisak-valve commented 5 years ago

Hello @m9115m, does the 2018-11-23 Steam client beta update improve the clients behavior with regard to this issue?

m9115m commented 5 years ago

Let me take a quick look

Sent from my iPhone

On Nov 23, 2018, at 10:32 AM, kisak-valve notifications@github.com wrote:

Hello @m9115m, does the 2018-11-23 Steam client beta update improve the clients behavior with regard to this issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

m9115m commented 5 years ago

After clicking on Participate in Client Beta, in Big Picture Mode, this version was downloaded... 11-22-18 22:18

With the version, I notice the Web Component does behave differently...

But not the desire outcome when trying to purchase a game. Still the same behavior as above:
Enter payment info, transaction doesn't complete, just recycles the same screen.

Also noticed - and this bug may have already been there - that in Big Picture Mode, the web component does an extra refresh, when browsing the Discovery Queue, in the Linux client. Should I log this as a bug?