GuruStop.NET

Hey folks, I just removed the default WordPress search widget and a new one using the HTML 5 input search type, a bunch of CSS 3 (and fall back for older browsers like older versions of IE), and a little bit of JavaScript. It’s still based on the same background image used in this blog theme though.

Since some of you might be interested, here is the code that I use to implement it, instead of you trying to hack it with different browser developer tools!
Not the exact code though, but a version that is heavily commented for your convenience

You can skim quick over the the simple HTML, spend some time with the CSS bits (most work is done here), and have a look at the bonus JavaScript, see the result without the context of the blog itself, and if you feel excited, click the "+" icon on the right to start editing it yourself to come with better implementation or fix a bug.!

If you like this post, you may want to share the post or comment below encouraging me to write more similar posts, maybe also check what offers are available by bog partners, or, follow me on twitter (@Meligy).

While I was doing some timezone stuff (that will likely have its own post), I came across some gotachas browser around working with date and time in JavaScript (blame the browsers, not JS itself):

1. There are very nice ISO standards to model date and time, their support is flaky, especially in, yes, IE. So, if you want to use them, you need a library that parses your standard and deal with it nicely (yes, there are some).
2. If you try to format dates with dd/mm/yyy instead of mm/dd/yyyy (the American standard), browsers will will play messy, Some methods will simply invert the values (They will think the day 30 is June, maybe as 30-12-12=6, and some methods may fail to parse getting you NaNs and "Invalid Date"s getting values of fields and trying to convert to string). They’re not broken in consistent way I think.
   The important note is that setting language preferences in browsers to "not" include English (US) does not change this.
3. The "toString()" implementation of date objects in browsers is not exactly the same. For example, IE might try saying "UTC+1100 2010" at the end for EAST with daylight saving on, while Chrome will say "AUS Eastern Daylight Time".

Well, let me just share this email with you… *

OK, instead of much talk, let me quote you the email that says all 1-day deals by SitePoint in last 23 days are available today. I’m not sure of the time zone for “today”, so, ne quick!

The time has almost arrived to tear open our presents …
But before we do that …

You know all those cool deals you missed? Don’t despair!
We’ve brought them all back and you can scoop up any deals
you missed out on while saving up to 90%!
http://sale.sitepoint.com/

 

To ensure the accuracy of your orders, each deal must be processed
individually. This means we’re unable to combine shipping costs.
However, the prices are so low, you’ll still be saving bucket loads.

 

Thank you for participating in our Christmas Countdown!

 

We hope you’ve enjoyed the deals we’ve had to offer as much
as we’ve enjoyed sharing them with you.
Happy Holidays and all the best for a prosperous 2011! :)

 

The SitePoint crew

Go and pick the offer that sounds good for you. Do not worry about the "X" on each.