This is a Page Loading bug and therefore I should be attacking it and doing reductions and figuring the issues and all that - but I just don't have the time right now...
But, as Starcraft 2 is now public, I predict a lot of interest - I'll be the first to file it ;)
Go to the above url - http://starcraft2.com/features/protoss/
There is a blue navigation section near the top to select from (currently) 4 units and 1 building. I say currently because the site is in its 1st day live and I predict it will be altered quickly as info about SC2 comes out.
By default, this page is giving you the detailed view on the "Zealot" unit. There is a heading "Zealot" above the description and a little plugin showing the Zealot 3d model animation.
Click on the 2nd unit in the unit list - should be the "Immortal" unit. After the navigation, the page should be layed out the same, with "Immortal" replacing "Zealot" and the animation should now be a different unit.
Instead, there is no heading for the new page and the animation area is now blank.
FFX demonstrates the correct and expected behavior
My current WebKit revision is 21600
I hope someone can make a reduction of this pretty soon :) (I will be able to, but in a few days)
Since any WoW related bugs are automatically given P1 treatment, I'm tempted to do so here because SC2 will undoubtedly be "WoW"ish in popularity and importance.
Once the game is released, that is... I'll hold off for now :)
Created attachment 14630 [details]
How the first unit detail view (Zealot) looks, and how all of them should look
Created attachment 14631 [details]
Here's the second unit - notice no unit name and blank area for the unit animation
Another Starcraft II bug: Bug 13790. Not sure if they're related or not.
Looks like the site fixed this a long time ago, and since we don't have anything saved I doubt we can reproduce and fix this.
(In reply to comment #6)
> Looks like the site fixed this a long time ago, and since we don't have
> anything saved I doubt we can reproduce and fix this.
The Internet Archive has a page from May 21, 2007 archived:
Unfortunately, I think the archived page relies on some server-side resources (e.g., XMLHTTPRequest), so it still doesn't help.
Marking as RESOLVED/WONTFIX since we can't reproduce the issue anymore.