After months of anticipation and three Release Candidates, the new version of Firefox is now available for download. (Due to demand, servers are still a bit slow, so just keep trying and you will eventually get it!).
Most common developer plugins were updated to support FF3 in the last week or so:
Cheers!
I found a few references to this lately and just had to look into it. This is similar to the FAVICON approach used in browsers, but supports a (60×60), officially a 57×57 pixel icon.
The code is simple:
<link rel="apple-touch-icon" type="image/jpeg" href="/example.jpg" /> References:
Old Reference (no longer works):
Cheers
Okay, so this is a little odd. This does not effect the language or direction of the website, but instead is a measure to ensure proper encoding of the CSS file itself.
The browser will generally rely on the HTTP Headers to determine this value, but in cases where the server or application configuration does not, you can provide the equivalent in the file itself.
WARNING: This needs to be the first line of the .css file, before any spaces or comments.
Example:
@charset “UTF-8”;
Other common value:
@charset “ISO-8859-1”;
Reference:
http://www.w3.org/International/questions/qa-css-charset
Cheers!
I was recently looking back at some websites I’d created years ago and realized just how much of a hastle the HTML FORM tag used to be for page layouts. This generally resulted in non-valid markup where the FORM tags themselves were improperly nested in TABLE, TR and TD tags.
Other than the obvious accessibility and semantic markup issues, there are two specific items that must be realized about the layout when working with a FORM.
The following examples assume the following source:
Hello<form>Again</form>World
FORM is a block element, forcing content around it to be separated:
Example displays as:
Hello
Again
World
Example displays as:
Hello
Again
World
<style type=”text/css”>
form { margin-bottom:0; display:inline; }
</style>
Example displays as:
HelloAgainWorld
Cheers!