Replace In-Steam Browser with Chrome

[Snorkel]

Huh! You can CTRL-F in the browser now! WOOOO!

I still miss the ability to CTRL-ENTER to quickly enter a URL. (ie typing "google" and then ctrl-enter to put www. in front and .com on the end).

In fact, it would be good if it had a button to quickly take someone to google. Or the ability to set a few bookmarks.

And I miss the way a normal web browser changes the focus to the page once it's loaded. Steam browser seems to keep it in the address box.

[jmccaskey]

Originally Posted by Zerias

question: There was a discussion on the Skia Google Group list a while back about rendering Skia into an existing OpenGL context: https://groups.google.com/group/skia...1e6e356ec6c328

Has Valve played around with this capability of Skia, or is this something that nobody has had time to look at yet?

It's not really a solution to the problem. The Skia opengl backend has different (read: not always better) performance characteristics and it doesn't get rid of the need for a texture copy as most games are not running in OpenGL and you can't share textures directly between OpenGl and D3D. Additionally, we've isolated the chromium code into a separate out-of-game process (gameoverlayui.exe) to avoid letting it ever crash the game. It's actually the least stable component in our overlay and responsible for a majority of crashes (mostly due to plugins, not the Chrome code itself). Since it's isolated to a separate process this also makes it more complicated to share a direct GL surface even if the game is OpenGl. The separation is pretty important as right now if a bad page/plugin crashes the process you just end up with the overlay disappearing for a second then restarting, and your chat messages even get preserved. If it was in-game the game would crash and you'd lose progress.

[Zerias]

Originally Posted by jmccaskey

It's not really a solution to the problem. The Skia opengl backend has different (read: not always better) performance characteristics and it doesn't get rid of the need for a texture copy as most games are not running in OpenGL and you can't share textures directly between OpenGl and D3D. Additionally, we've isolated the chromium code into a separate out-of-game process (gameoverlayui.exe) to avoid letting it ever crash the game. It's actually the least stable component in our overlay and responsible for a majority of crashes (mostly due to plugins, not the Chrome code itself). Since it's isolated to a separate process this also makes it more complicated to share a direct GL surface even if the game is OpenGl. The separation is pretty important as right now if a bad page/plugin crashes the process you just end up with the overlay disappearing for a second then restarting, and your chat messages even get preserved. If it was in-game the game would crash and you'd lose progress.

Thank you for explaining this.

[Mangr0v3]

Originally Posted by jmccaskey

Additionally, we've isolated the chromium code into a separate out-of-game process (gameoverlayui.exe) to avoid letting it ever crash the game. It's actually the least stable component in our overlay and responsible for a majority of crashes (mostly due to plugins, not the Chrome code itself). Since it's isolated to a separate process this also makes it more complicated to share a direct GL surface even if the game is OpenGl. The separation is pretty important as right now if a bad page/plugin crashes the process you just end up with the overlay disappearing for a second then restarting, and your chat messages even get preserved. If it was in-game the game would crash and you'd lose progress.

I thought Chromium had process separation of it's own?