Re:We Built Interactive Seating Maps Using Raphael; Please G...
by antidaily on Friday September 10, 2010 @02:34PM
(#1679736)
Not loading for me - Chrome, OSX.
[ Parent
| on HN ]
Re:We Built Interactive Seating Maps Using Raphael; Please G...
by ay on Saturday September 11, 2010 @05:17AM
(#1681252)
Not sure if original link is direct to seating - but if it is, it does not render on my HTC desire with Android 2.2 and mobile safari. I use Raphael on one of my websites and have similar problem there.
Re:We Built Interactive Seating Maps Using Raphael; Please G...
by algolicious on Saturday September 11, 2010 @01:13PM
(#1681873)
Doesn't work on my Droid with 2.2 either. I loaded it twice, over twelve hours apart, from different locations. Just shows a gray rectangle where the tickets should be (after showing the loading animated gif for several painful seconds) and a white area where the stadium should be. Works fine on Firefox. I think it is important to support mobile - at work, one may rather not have their employer know that they are spending time looking for tickets. Hopefully it is possible to give a good experience. The chrome takes up most of the display in landscape mode, though when I rotate to portrait, there is much more space.
One other thing: is there any way to keep the dots from displaying until the map is loaded? It is jarring for me to see them floating out in white space. Yet when the map is cached, the map displays before the dots.
Re:We Built Interactive Seating Maps Using Raphael; Please G...
by wmeredith on Friday September 10, 2010 @02:34PM
(#1679738)
Not loading for me as well - Safari 5.0.2, OS X
Re:We Built Interactive Seating Maps Using Raphael; Please G...
by kertap on Friday September 10, 2010 @02:38PM
(#1679754)
It didn't load for me either. It seems to be just that game though because this one worked for me. http://seatgeek.com/event/show/457428/green-bay-packers-at-p...
Re:We Built Interactive Seating Maps Using Raphael; Please G...
by josegonzalez on Friday September 10, 2010 @02:45PM
(#1679786)
Seems to be a caching bug, we've redeployed and all is no longer lost :) Please try again, we definitely appreciate finding edge-cases like these.