it's supposed to enable access to various support sites in-game. on the mac they're running chrome. not sure about windows (tho i do see an instance of WebBrowserProxy.exe running for each instance of wow... crushing my machine)
anyone have any experience with the new widget?
can we bring up various blizz sites in-game? if so, how?
They're also running Chrome on Windows, which makes it completely unusable for anyone running a third-party font rendering engine to improve text legibility since Chrome fails horribly in this situtation, resulting in distorted, nearly invisible text. Also, it's the only program I've ever seen or heard of that has this problem, so despite the Chrome devs claiming it's a bug in the font renderer, I'm still blaming in on Chrome for not using the same methods to render text as every other application in existence. Even with default Windows font rendering (ClearType on/off doesn't matter) Chrome's text rendering is atrocious... it's like they somehow missed the invention of anti-aliasing.
Also, the in-game browser widget isn't zoomable or resizable at all... my roommate who is way more blind than me can't really read it even when he disables gdi++.
There is no URL bar, so you can only get to pages that are linked to from the Battle.net support site, and maybe not even all of those; I only looked at it for about 30 seconds before deciding it was completely useless.
It's also really annoying when I open the Help window to report a bug and have to wait for the browser widget to load. I just kill the WowBrowserProxy.exe process, and it's already on my to-do list to set up AutoHotkey to automatically kill it any time it appears.
All in all it seems like a big failure, but I'm sure there are some people who will love it.
Yes, they are using an embedded Chrome browser. Writing your own rendering engine for web content is not really feasible these days (though maybe slightly feasible if you're only ever going to be rendering your own HTML documents) but yeah, I don't know why they aren't using the browser in the user's OS. Maybe it's harder to support multiple platforms that way?
Its really an easy choice to embed a portable browser these days.
And despite everyones complaints, if you can't use it, you don't miss out on anything that you could before, its additional ingame support, just open your normal browser if you dont like the ingame one ;)
Well, you are missing out on the ability to submit tickets in-game, which is pretty annoying. Also, in my experience, GMs don't respond in-game to tickets that weren't submitted in-game; that may have changed now, but if not, that's also a pretty big annoyance.
Given that all the GM chat thingy is still in the FrameXML, it's quite possible the in-game browser signals itself as such (using the User-Agent HTTP header), so they can identify these tickets and answer accordingly.
I agree that's still a problem for people with considerable visual impairments.