CSS / JavaScript / HTML5
I’m going to come right out and say that it’s likely to take IE years before we see native HTML 5 support. However, that doesn’t mean we should ignore HTML 5 until IE gets with the program.
If you’ve tried to mess around with HTML 5 in IE, you may have noticed that the new elements do not work correctly with css. Luckily for us, we can use a tiny bit of Javascript to trick IE into rending the HTML 5 elements correctly.
AjaxPages allows you to serve up full pages completely with ajax. This is very useful if you want to build a site that has a music player running across page loads, but don’t want to use frames. This technique can be found at TheSixtyOne.
All internal links should be in hash format. Example: instead of linking to filename.html, you would link to #/filename.html.
If you have clean urls on, the hash is almost not noticeable. Example: domain.com/#/profile/username
To get started with AjaxPages, get the files from the Google Code trunk. Example files are included. That should be enough to get you started. The plugin is very lightweight and fairly simple so it should not give you any problems.
If you need help, please leave a comment and I will personally help you out.
I got fed up with the numerous amounts of plugins that handle custom checkboxes and radio inputs that I decided to create my own. Typically, the plugin will create html for you in which you an style. But you also have to pass in url’s for images that will be used for the various states.
The plugin I created, bltcheckbox, allows you to use any html and css. The only options you pass to the plugin are whether it’s a checkbox, or a radio input.
For code samples and documentation, please check out the code code page here.
As it turns out, Microsoft really doesn’t care about web standards at all. It has taken them way too many years to adopt the basics of CSS2 correctly. Now they are trying to expand that with IE8. However, developers still have to deal with the outdated IE6 and IE7. Using min-width is completely pointless unless your user base only uses good browsers. Read the rest of this entry »
If you have worked with AJAX at all, you know that there is this thing called the Same-Origin policy which makes it nearly impossible to send AJAX requests to 3rd party domains. There are workarounds such as going through a proxy. I don’t like that and think it’s messy. However, sometimes it’s the only way to go about getting the job done. This post is not about going through a proxy, instead, it is about using a little trick I learned from Yahoo. Read the rest of this entry »