web 3.0 » Código

¿Así que querías saber (casi todo) de CSS?

bevilacqua — Sat, 18 Apr 2009 01:11:11 +0000

SEO-sanitizing a WordPress theme in 5 minutes

emoticon — Thu, 08 May 2008 14:36:08 +0000

When you start a blog with WordPress, you get an overall good crawlability like with most blogging platforms. To get it ranked at search engines your first priority should be to introduce it to your communities acquiring some initial link love. However, those natural links come with disadvantages: canonicalization issues.
“

CSS RESET – ACTUALIZACIÓN FEB08

emoticon — Fri, 15 Feb 2008 08:21:39 +0000

http://meyerweb.com/eric/tools/css/reset/reset.css

/* v1.0 | 20080212 */
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
padding: 0;
border: 0;
outline: 0;
font-size: 100%;
vertical-align: baseline;
background: transparent;
}
body {
line-height: 1;
}
ol, ul {
list-style: none;
}
blockquote, q {
quotes: none;
}
blockquote:before, blockquote:after,
q:before, q:after {
content: '';
content: none;
}
/* remember to define focus styles! */
:focus {
outline: 0;
}
/* remember to highlight inserts somehow! */
ins {
text-decoration: none;
}
del {
text-decoration: line-through;
}
/* tables still need 'cellspacing="0"' in the markup */
table {
border-collapse: collapse;
border-spacing: 0;
}

IE8 : “browser version targeting”

emoticon — Sat, 02 Feb 2008 00:23:01 +0000

Microsoft has announced that IE8 will introduce a new “browser version targeting” system that will see the browser default to rendering standards-compliant pages the same as in IE7, and will require developers to explicitly opt in to IE8′s new, Acid2-compliant rendering engine if they want it.
Furthermore, since Microsoft believes this is the best way for all browsers to move the Web forward without breaking current sites, it has implemented this opt-in mechanism in a form that all browsers can support:

When placed in the head of an HTML page, this tag will tell IE8 or later to render the page using the most advanced (and standards-compliant) rendering engine available in IE8, instead of the default, IE7-level rendering mode.
In the future, other browsers may implement this standard too, if they find it useful (more on this below):

If you wish to avoid adding a tag to all of your pages, you can instead configure your web server to send the same information as an HTTP response header, though if history is any guide, the tag will be by far the preferred mechanism.
And if you prefer the current browser behavior of always using the most standards compliant rendering available for the document’s DOCTYPE, you can use the special edge value to request that:

But Microsoft believes this is not what most people will want if they stop and think about it. Mainly, this feature is there for experimental/demo pages (such as the Acid2 test).
By requiring developers to declare when they want new browser rendering engines to kick in, Microsoft hopes to eliminate the kinds of page layout issues that plagued the release of IE7. From now on, if you write a page for a particular version of IE, it should work in all future versions of IE.
This move, if embraced by developers, would represent a fundamental shift in the role of standards on the Web. Understandably, quite a few people are upset by this”

Noscript – js deshabilitado

emoticon — Thu, 20 Jul 2006 00:09:21 +0000

Para los navegadores que tienen JS deshabilitado:

corchete noscript corchete
corchete meta http-equiv=”refresh” content=”0; URL=http://www.url.com/noscript.htm” corchete
corchete / noscript corchete

La movida de las esquinas redondas

emoticon — Mon, 23 Jan 2006 03:42:02 +0000

Gracias a http://www.albin.net/CSS/roundedCorners/ por compartir esto

XHTML:
/ver en url albin.net
CSS:
.roundedCornerSpacer {
margin: 0px; padding: 0px; border: 0px;
clear: both;
font-size: 1px; line-height: 1px;
}
/* In the CSS below, the numbers used are the following:
1px: the width of the border
3px: a fudge factor needed for IE5/win (see below)
4px: the width of the border (1px) plus the 3px IE5/win fudge factor
14px: the width or height of the border image
*/
.borderTL, .borderTR, .borderBL, .borderBR {
width: 14px; height: 14px;
padding: 0px; border: 0px;
z-index: 99;
}
.borderTL, .borderBL { float: left; clear: both; }
.borderTR, .borderBR { float: right; clear: right; }
.borderTL { margin: -1px 0px 0px -1px; }
.borderTR { margin: -1px -1px 0px 0px; }
.borderBL { margin: -14px 0px 0px 0px; }
.borderBR { margin: -14px 0px 0px 0px; }
/* IE5-5.5/win needs the border scooted to the left or right by an
additional 3px! Why? */
.borderTL {
margin-left: -4px;
margin-left: -1px;
}
html>body .borderTL {
margin-left: -1px;
}
.borderTR {
margin-right: -4px;
margin-right: -1px;
}
html>body .borderTR {
margin-right: -1px;
}
.borderBL {
margin-left: -3px;
margin-left: 0px;
}
html>body .borderBL {
margin-left: 0px;
}
.borderBR {
margin-right: -3px;
margin-right: 0px;
}
html>body .borderBR {
margin-right: 0px;
}
/* To get around a known bug in IE5/win, apply the
border (no margin, padding or positioning) to the
content class and apply whatever positioning you
want to the contentWrapper class. */
.content {
margin: 0px;
padding: 0px;
border: 1px solid #00000;
}
.contentWrapper {
/* position this div however you want, but
keep its padding and border at zero */
padding: 0px;
border: 0px;
}