Sometimes it says "K2.HTML.Lockup.Updated" and sometimes it says "K2.HTML.Lockup.Upd..."

I tweeted about it and didn’t get any tweets back but I got a lot of hits on this website when that phrase came up in my twitter feed. Looks like many other people are getting it to.

iOS App store parsing error :) K2.HTML.LOCKUP.UPDATED http://t.co/NSUW5TU4

December 7, 2011 10:26 pm via Twitter for iPadReplyRetweetFavorite

@soniiic

Dan Cooper

I’m guessing it’s a parsing error and it’s what Apple use to display that particular app’s last updated date.

When rolling over a number of flyouts quickly, the user sees all the flyouts shown on the screen at once which looks rubbish.  To remove the delay altogether use this css in your page somewhere:

li.hover-off>ul
{
    display:none;
}

The way it works is when you hover over an item in the nav the built in sharepoint javascript adds a css class called “hover” and as soon as your mouse leaves the area it changes the class to “hover-off” for 1 second before removing it completely. This CSS will hide the unordered list directly below the list item that has the class “hover-off” thus hiding the flyout as soon as your mouse leaves the parent.

(P.s. this kind of flyout navigation can be set up by setting the ‘MaximumDynamicDisplayLevels’ attribute of the SharePoint:AspMenu control)

There are a number of ways to emphasise the primary action. One of the easiest and yet still effective methods is to colour the button brightly to draw attention. Similarly you could reduce the saturation of the cancel button. The human eye is drawn to areas of colour which stand out from the page. Also culturally the colour green is associated with a positive action and so if the user is in a hurry or just speedily going through the form, when they see the green button they will know it’s the button that submits the information. Chances are that they won’t actually read the text of the button!

Notice how the send button is all bright and cheery in the facebook-blue colour whereas the cancel button is grey and boring.  Other methods are also just as effective such as using a text link for the cancel action instead of a button.  This is the one I much prefer as it informs the user that by pressing the link, it’s not going to post anything they’ve typed in on the form.  Perhaps less tech-savvy users might think the cancel button would perform some function if they typed in their order details and requested to ‘Cancel’ the order.  A link would completely resolve any issues as a normal web user knows that a link just redirects to a different page (in most cases).

Below we see a text link being used to give the user the opportunity to cancel the submission and return to where they came from.

Also it might be worth noting that rarely is the ‘reset’ button used on forms now.  I don’t know why it ever caught on in the first place anyway… Who wants to fill out an entire form and then scroll to the bottom and press reset?  It provides functionality that I’m sure was never used and when it was used it was never intended(!)