5 ms·
Yes, I too was blocked from further exploring by this bug. Why so much clicking? Wouldn't it be much better if the box with information simply appeared when mou
by vlasta2 14y ago
Yes, I too was blocked from further exploring by this bug. Why so much clicking? Wouldn't it be much better if the box with information simply appeared when mouse hovers over the circle?
- duiker101 14y agoI usually do not like mouse hover to popup but at least they should have made the background clickable to hide the popup.
- tripzilch 14y agoHow about just: All the logo-buttons on top. Infoboxes neatly stacked below them (with enough whitespace of course), all of them visible. Button links to the corresponding infobox's fragment identifier. No waiting for animations to finish, no effects, no reducing the scrolling to 2 fps on the average netbook (which made me give up after clicking two buttons, thanks to the position:fixed elements, on 1366x768 you have to scroll to center the infobox vertically, which is pretty hard to do when it moves this clunky), additionally you can just read the infoboxes one by one if you happen to be interested in all of them, and you can even use the browser's built-in find-in-page search to find something specific. All that functionality missed out on, just because they needed to fade the button's border to brownred in the most inefficient manner imaginable. Maybe it's something else, but somewhere there's a zillion of event-listeners firing away at nothing. BTW you can almost get the functionality I described if you switch off CSS and JS and reload the page :) They already used the fragment identifiers, got so far and then made it nearly unusable with some JS effects framework ...
- Cyranix 14y agoI used to think this way too, but the rise of touchscreen devices has meant that hover-based events restrict your audience.
- dllthomas 14y agoSo why not pop up a transient box on hover and a persistent box on click?
- criswell 14y agoThis is tabular data gone awry.