I like this approach to deal with a large area of negative space. Whilst one could resize the modal window to fit the contents, that becomes a pain when trying to maintain consistency and reduce code complexity. This approach puts some feeling and fun back into an otherwise emotionless interface and is the sort of thing that people find special and memorable. Well at least this person does.
Nice work! More of this.
Comments [0]
Comments [0]
http://soundcloud.com have a great UI pattern for blocking or 'muting' people you follow..
UI for blocking has always been problematic for service architects. On the one hand you don't want to make the interface for blocking so attractive that everyone does it, and on the other hand you dont want to obscure it so much so that people don't know about it and cant control the stream of data coming down the pipe from others.
They have also made the consequences of the action very clear with the resulting modal window that explains in great deal the effects of this action.
I must admit when I first noticed it I though it meant mute the track that was playing at that time shared by mnml ssgs not mute mnml ssgs which is what the action is. Luckily they go into great detail about what happens as a result in the modal window. A far better approach than the traditional
Are you sure you want to mute this user?
[ O K ] Cancel
Another issue I think they have dealt nicely with is the actions menu. Same sort of issues here as the last one. Don't want to make the visual repetition of an actions menu button/trigger so loud that it becomes distracting, yet don't want to bury it so no one can find it.
The light grey row ending and row color highlighting are visually unobtrusive and the size an placement of the menu on the right feels natural.
There is also the added bonus of being able to avoid it as it will always stay in the same place on the screen as you scroll down the page. Just keep your pointer to the right. of the content
There is nothing worse than things popping up all over the page as you scroll down and your inactive pointer inadvertently triggers a menu.Thumbs up from me, no forking needed here. Soundcloud +1
Great site on so many other levels as well, sign up and check it out, its free to join.
Comments [0]
Comments [0]
Comments [0]
But thanks to people like Henri Sivonen it is a little easier to makes sense of all the forks in the code.
Check out his epic page to take the sense out and put the science in to random browser behaviour using the doctype delaration.
Nicely done.
Comments [0]
Pic by Dunechaser via flickr
That is until you stole them way from me IE.
I used to go digging in my backyard looking for ancient artifacts. Even found some too.
But thanks to you IE, I now spend my time worrying about box models, web standards and cross browser support.
Way to go IE you ruined my life! Way to take a young boy's dreams and smash them to smithereens.
Good Job.
Comments [0]
Pic by ndanger via Flickr
That is correct.
IE7 will take your pretty little disabled 24bit .png icon with transparency
.diasbled {
opacity: .5;
filter: alpha(opacity=50);
}
and smash it's brains against the wall so that you can see its inner workings.
Thanks IE7 for ruining the magic.
*Actually happens in ie8 as well
Comments [0]
Pic by Gabriel Dieter via Flickr
Not only does IE7 not allow you to control the border of an iframe with css, the attribute is bloody case sensitive!
NO: frameborder
YES: frameBorder
M$FT put a fork in it, its done.
Comments [0]
Pic by Exey Panteleev via Flickr
Apparantly IE7 renders elements that are further down the document above those that come earlier, regardless of the z-index.
In effect, this renders the z-index thing pretty much entirly useless.
There is a fix, wrap it in another element like a div and set the z-index of that element to a higher z-index.
(kinda like putting your pants on before busting out of them)
IE7, GET FORKED!
Comments [0]
Visual, information, experience and interaction design are my thing.
Follow me up on http://twitter.com/chopps
