-
Notifications
You must be signed in to change notification settings - Fork 13
/
easyclearing.html
executable file
·634 lines (499 loc) · 24.4 KB
/
easyclearing.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Clearing a float container without source markup</title>
<meta http-equiv="content-Type" content="text/html; charset=iso-8859-1" />
<meta name="mssmarttagspreventparsing" content="true" />
<meta name="description" content="This demo shows a bug in IE when multiple floats are in a 'widthless' container." />
<meta name="distribution" content="global" />
<meta name="resource-type" content="document" />
<meta name="robots" content="all" />
<meta http-equiv="imagetoolbar" content="no" />
<link rel="SHORTCUT ICON" href="favicon.ico" />
<script type="text/javascript">
if (window.self != window.top) window.top.location = window.self.location;
/* break my page out of any naughty framer's site. */
</script>
<style type="text/css">
html {
margin: 0;
padding: 0;
border: 0;
}
body {
margin: 0;
padding: 0;
font-size: 100.01%;
background: #f8eedd;
font-family: verdana,sans-serif;
}
h1 {font-size: 1.4em; border-bottom: 3px solid #fff; background: #000;
margin-top: 0; color: #fff; padding: 3px 0 3px 3em;}
h2 {font-size: 1.2em; font-weight: bold; margin: 2.5em 10% .5em;}
h3 {font-size: 1.1em; font-weight: bold; margin: 1.5em 13% .5em;}
.textbox {margin: 2em 0 3em; font-size: .8em;}
.textbox p {margin: .6em 18% .6em 18%; padding: 0;}
blockquote {margin: 1.6em 22% 1.6em; padding: 0;}
.red {color: #d00;}
a {color: #000;}
.alignright {margin: 0 30px 30px 0; text-align: right;}
.small {font-size: .9em;}
pre {margin: 30px 8%; padding: 20px 10px 20px 30px; background: #f0ddb8;
border: 2px solid #000; font-size: 120%; font-weight: bold; font-family: "courier new", monospace;}
pre span {color: #d00;}
ul {text-align: right; padding-right: 30px; list-style: none; font-size: .9em;}
.textbox .imageholder {padding: 20px 0 20px;}
p.alert {border: 1px solid #c00; background: white; padding: 10px; margin: 20px 25%; font-weight: bold;}
/*XXXXXXXXXXXXXXXXXXXX First Demo rules start here XXXXXXXXXXXXXXXXXXXXXXX*/
.guillotine-box {
float: left;
width: 200px;
border: 4px solid #5a5;
background: #ddd;
margin: 0 40px 10px 0;
color: #fff;
font-size: .8em;
}
.guillotine-float {
float: right;
width: 130px;
border: 3px solid #ff8;
background: #766;
color: #ffd;
}
.guillotine-box a:hover {
background: #aaa; /*** Any hovered BG will trigger bug ***/
}
/*XXXXXXXXXXXXXXXXXXXX Second Demo rules start here XXXXXXXXXXXXXXXXXXXXXXX*/
.floatholder {
border: 4px solid #000;
margin: 10px 0 0;
background: #dc8;
font-size: 1.2em;
}
.floatbox {
float: left;
width: 35%;
background: #773;
border: 3px solid #f55;
color: #ffd;
}
.floatbox p {margin: 0;}
.floatholder p {margin: 0;}
.clearfix:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
.clearfix {display: inline-block;} /* for IE/Mac */
</style>
<!--[if IE]>
<style type="text/css">
.clearfix {
zoom: 1; /* triggers hasLayout and clearing effect */
display: block; /* resets display for IE/Win */
} /* Only IE can see inside the conditional comment and read this CSS rule.
Don't ever use a normal HTML comment inside the CC or it will close prematurely. */
</style>
<![endif]-->
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script type="text/javascript" src="/scripts/init.js"></script>
</head>
<body>
<h1>How To Clear Floats Without Structural Markup</h1>
<ul>
<li><a href="index-2.html"><strong>Return to PIE</strong></a></li>
</ul>
<div class="textbox">
<p style="text-align: right;">
<em>(This clearing technique was developed by Tony Aslett, of csscreator.com. <br />
The earliest known mention of the basic :after idea is found
<a href="http://lists.w3.org/Archives/Public/www-style/2002Aug/0134.html">here</a>.)</em>
</p>
<p class="alert">
Notice as of March 4th, 2008: The article you are reading is getting a bit old and much new information on the subject of clearing has appeared since it was written.
You may find <a href="http://www.sitepoint.com/blogs/2005/02/26/simple-clearing-of-floats/">this newer article</a> very interesting.
</p>
<h2 style="margin-top: 30px;">Clearing Floats The Old Fashioned Way</h2>
<p>
When a float is contained within a container box that has a visible border or background, that float does
<em>not</em> automatically force the container's bottom edge down as the float is made taller. Instead the float is
ignored by the container and will hang down out of the container bottom like a flag. Those familiar only
with Explorer for Windows may scratch their heads and say "That's not right!" True, IE/Win does enclose
a float within a container 'automatically', but only if the container element happens to possess the MS-only
quality called
<a href="http://www.satzansatz.de/cssd/onhavinglayout.html"><strong>hasLayout</strong></a>.
</p>
<p>
This float-enclosing behavior in IE can also be 'toggled' off again just by hovering of links within the container,
if that hovering alters either the link background or one of several other CSS properties. Quite a mess,
and we'll cover it farther along in the article, in the "Toggle Trouble" section.
</p>
<p>
The W3C suggests placing a "cleared" element last in the container box, which is then recognized by the
container height, forcing the container to enclose the float above that cleared element too. It's described
more fully our article <a href="articles/float-theory.html">Float: The Theory</a>:
</p>
<blockquote>
“..let's say you give that following box the clear property,
<span class="red"> {clear: both;} </span>.
What this does is extend the margin on the top of the cleared box, pushing
it down until it "clears" the bottom of the float. In other words, the top
margin on the cleared box (no matter what it may have been set to), is increased
<strong>by the browser</strong>, to whatever length is necessary to keep
the cleared box below the float.”
</blockquote>
<p>
So in effect, such a cleared box cannot be at the same horizontal level
as a preceding float. It must appear just below that level. The image shows
how this might look, with a red border representing the container element:
</p>
<div style="margin: 20px 0 20px; text-align: center;">
<img src="articles/images/clear-box.gif" width="450px" height="248px"
alt="Shows how a box may clear below a float." />
</div>
<p>
The standard method of making an outer container <em>appear</em> to "enclose"
a nested float is to place a <strong>complete "cleared" element</strong>
last in the container, which has the effect of 'dragging' the lower edge of the containing box lower
than the float. Thus the float appears to be enclosed within the container even tho it really isn't.
The code for a cleared box usually looks something like this:
</p>
<pre>
<div> <!-- float container --><br />
<div style="float:left; width:30%;"><p>Some content</p></div><br />
<p>Text not inside the float</p><br />
<div style="clear:both;"></div><br />
</div>
</pre>
<p>
Since that div is not floated, the container must recognize it and enclose
it, and because of that top margin (added by the browser because of the
"clear" property), the div "pulls" the bottom edge of the container down
below the bottom edge of the float.
</p>
<h2>Problems With The Method</h2>
<p>
First and foremost, this clearing method is not at all intuitive, requiring an extra element be added to the markup.
One of the major premises of CSS is that it helps reduce the bloated HTML markup found it the average site these days.
So having to re-bloat the markup just so floats can be kept within their containers is not an ideal arrangement.
</p>
<p>
Besides that, some browsers can have trouble with certain kinds of clearing elements in some situations.
Mozilla is particularly sensitive to clearing problems.
</p>
<p>
Up 'til now there was no other way to do this, but no more! Thanks to the efforts of <strong>Tony Aslett</strong>,
creator and operator of <a href="http://www.csscreator.com/"><strong>csscreator.com</strong></a>, we can now use advanced
CSS to "clear" a float container in non-IE browsers and just let IE keep wrongly clearing itself. The upshot is that we now have
the option to avoid adding that pesky clearing element to the HTML markup. Woohoo!
</p>
<h2>"Clearing", 21st Century Style</h2>
<p>
In the new method, <em>no clearing element is used</em>. This does not affect IE/Win which simply keeps enclosing the
float as always (assuming the container has a stated dimension), but non-IE browsers will need a substitute for
that element. Here's how it's done.
</p>
<h3>Using :after</h3>
<p>
This <a href="http://www.w3.org/TR/REC-CSS2/generate.html#x5">CSS 2 property</a> allows extra content to be
added at the end of an element via the CSS. That means no actual markup is needed in the HTML. The content is
specified from within the CSS stylesheet, and appears in the page as would a real HTML element that had been
inserted following all the normal content of the target element. Such <strong>:after</strong> generated content cannot receive some CSS properties,
including 'position', 'float', list properties, and table properties. However, the 'clear' property <em>is</em> allowed.
Do you see where we are going here?
</p>
<p>
Imagine that we use <strong>:after</strong> to insert a simple character like a 'period', and then
give that generated element
<span class="red"> {clear: both;} </span>. That's all you really need to do the job, but no one wants
a line space messing up the end of their clean container box, so we also use
<span class="red"> {height: 0;} </span> and
<span class="red"> {visibility: hidden;} </span> to keep our period from showing.
</p>
<pre>
.clearfix:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
</pre>
<p>
Notice that <span class="red"> {display: block;} </span> is also applied to the :after
element, because if it isn't then that element defaults to "inline", and cannot receive the "clear" property.
Also, Tony's method originally used "overflow: hidden;" to hide the period, but sadly the latest FireFox versions
will display the period if this is done.
</p>
<h3>But what about IE?</h3>
<p>
Since IE7 does not support the :after pseudoclass yet, we must rely on the same"auto-clearing" effect used for IE6,
and that behavior happens when the float-containing element gets <strong>hasLayout</strong> applied to it.
A simple declaration of "zoom: 1;" will perform this trick in IE5.5 and up, but it's proprietary and needs to be
<a href="articles/haslayout.html"><strong>hidden</strong></a> in order to validate.
</p>
<p>
As a side benefit, hasLayout on float-enclosing elements also prevents several other major
IE/Win float bugs. However, should this container box be placed following a previous <em>external</em>
float, the IE height fix will trigger Microsoft's proprietary and illegal
<a href="articles/float-bugs-1.html">Float Model</a>, so watch out for that, okay?
</p>
<h3>Toggle Trouble</h3>
<p>
It so happens that IE has, well, a <em>little problem</em> with this auto-enclosing behavior. You saw
that coming, didn't you. Yes, IE bugs come in big bunches. This one results when that container element
has links inside, following the float. When this happens and certain links are hovered, the auto-enclosing
behavior is toggled or "switched off", causing the lower edge of the container box to suddenly jump up
to the bottom of the non-floated content. Hovering other links restores the behavior. This interesting
effect is of course called the <strong>IE/Win Guillotine Bug</strong>
Those of you viewing in IE/Win may play around with the following live demos, and for a more complete explanation see the
<a href="explorer/guillotine.html">IE/Win Guillotine Bug</a> demo page .
</p>
<p>
The toggling only occurs when <strong>a:hover</strong> is used to change the <strong>link background</strong>
or many other styling changes, such as <strong>padding</strong>, <strong>margin</strong>, or any
<strong>font</strong> styling on the link. Strangely, having the <strong>text color</strong>
change on hover does <em>not</em> toggle the bug.
</p>
<p>
The containers are grey with green borders, and the floats are dark brown with yellow borders.
Notice how the third and fourth links ouside the floats toggle the Guillotine Bug, and the first two
un-toggle it. This seems to be related to the actual text lines themselves, so any links after the first
two lines will toggle the effect. Links in the float will all un-toggle
the effect. Just more weird IE bug behaviors, folks, nothing "unusual".<br/>
<a href="images/guillotine.gif">Screenshot</a>
</p>
</div>
<div style="padding: 10px 10% 20px 22%;">
<div class="guillotine-box">
<div class="guillotine-float">
<a href="#">Float Link</a><br />
Any link in this float will restore the cutoff portion, as will the links in the first two text lines outside the float.
Something makes those first two lines "special".
</div>
<a href="#">Link</a><br />
<a href="#">Link</a><br />
<a href="#">Link</a><br />
<a href="#">Link</a><br />
</div>
<div class="guillotine-box">
<div class="guillotine-float">
<a href="#">Float Link</a><br />
The non-floated links to the left are wrapped in a paragraph, and that paragraph has the Holly hack value applied to it.
Say "buh-bye" to the Guillotine Bug!
</div>
<p class="clearfix" style="margin: 0;">
<a href="#">Link</a><br />
<a href="#">Link</a><br />
<a href="#">Link</a><br />
<a href="#">Link</a><br />
</p>
</div>
<div style="clear: both;"></div>
</div>
<div class="textbox">
<p>
The second demo has been "fixed" by placing those links in a paragraph, which then gets the zoom fix applied to it.
Any block element will do just as well here. Yes, this means another element is needed, but unlike a clearing div,
this paragraph is a "semantic" element. Text content really ought to be wrapped in semantic containers anyway, and
since we forward-thinking coders always have our content thusly contained, it's easy to apply the same .clearfix class
to one more element.
</p>
<h3>A Word About Floats In Floats</h3>
<p>
Observant readers will have noticed that the above demos have "enclosed" floats, even in Opera 7 and Mozilla!
This is because the demos themselves are floats, and all modern browsers (including IE, luckily) always let floats
enclose other floats. Of course there has to be an outer float, and it still threatens to break out of <em>its</em> container...
</p>
<h2>Putting It Together</h2>
<p>
First, this code gets added to the CSS stylesheet:
</p>
<pre>
<style type="text/css">
.clearfix:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
</style><!-- main stylesheet ends, CC with new stylesheet below... -->
<!--[if IE]>
<style type="text/css">
.clearfix {
zoom: 1; /* triggers hasLayout */
} /* Only IE can see inside the conditional comment
and read this CSS rule. Don't ever use a normal HTML
comment inside the CC or it will close prematurely. */
</style>
<![endif]--></pre>
<p style="margin-bottom: 20px;">
For the HTML, just add a class of <span class="red">.clearfix</span> to any element containing a float needing to be cleared,
plus any Guillotine-Bug-fixing block elements within the container.
That's it! It's not perfect, but it's a whole lot better than adding an entire extra 'dummy' element. Check out this live demo of the
fix in action:
</p>
<div style="margin: 0 20%; height: 1%;">
<!-- NOTE: This div wrapper prevents IE/Win in quirks mode from using BODY as the base for measuring the % width
on .floatholder. This wrapper must be dimensionally defined before IE<6 will use it as the percentage base. --->
<div class="floatholder">
<div class="floatbox">
<p>This float is not enclosed by the surrounding div container. </p>
</div>
<p>This container lacks the fix.</p>
</div>
<div style="height: 20px; clear: both;"></div> <!-- Just a spacer div between the demos -->
<div style="border: 4px solid #000;
margin: 10px 0 0;
background: #dc8;
font-size: 1.2em;" class="clearfix floatholder">
<!-- the "clearfix" classname MUST be the first class in the attribute for the JS to work! -->
<div class="floatbox">
<p>See how this float no longer protrudes out of the containing box, with no extra clearing element used in the container!</p>
</div>
<p>This float container has a class attribute of "clearfix", which applies the :after fix, or the Holly hack, depending on the browser.</p>
</div>
</div>
<h3>IE/Mac Strikes Back</h3>
<p>
All this is wonderful, but unfortunately IE for the Mac does not "auto-clear" floats, and also does not support
<strong>:after</strong>, and so is left out of the clearing party. What's to be done?
</p>
<p>
You might callously abandon IE/Mac, but consider that many people who use older Macs can't run Safari,
or several other modern browsers. Thankfully this browser has been dropped by Microsoft, and at some
future time the numbers of such IE/Mac users will become miniscule. Remember that even if a float
appears to stick out of a container, no content will actually be obscured. It just won't look as pretty for
those few viewers, that's all. Each author will have to decide on this issue according to their specific needs.
</p>
<p>
This page once described a Javascript method to force compliance in IE/Mac, but now thanks to
<a href="http://www.nolocation.com/"><strong>Mark Hadley</strong></a> and
<a href="http://www.loungepenguin.co.uk/indexno.htm"><strong>Matt Keogh</strong></a>
it's now possible
to dispense with that ugly Javascript and go with a straight CSS fix. Woohoo!
</p>
<h3>Taming the IE/Mac Float Problem</h3>
<p>
Basically the fix is just a matter of applying a <strong>display: inline-block;</strong>
to the <strong>.clearfix</strong> class, and hiding that property from all other
browsers. That's it! We can easily do this with our existing code, slightly modified.
</p>
<pre>
<style type="text/css">
.clearfix:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
<span style="color: #a00;">.clearfix {display: inline-block;} /* for IE/Mac */</span>
</style><!-- main stylesheet ends, CC with new stylesheet below... -->
<!--[if IE]>
<style type="text/css">
.clearfix {
zoom: 1; /* triggers hasLayout */
<span style="color: #a00;">display: block; /* resets display for IE/Win */</span>
} /* Only IE can see inside the conditional comment
and read this CSS rule. Don't ever use a normal HTML
comment inside the CC or it will close prematurely. */
</style>
<![endif]--></pre>
<p>
The <strong>.clearfix {display: inline-block;}</strong> is seen by all browsers, and fixes IE/Mac.
Then, inside the rule set that is hidden from IE/Mac, the display is reset to <strong>block</strong>.
That's all she wrote! Simply stick the above code into your CSS, and use <strong>.clearfix</strong>
on any box that has to contain a sizable float. Ain't that cool? Just watch out for previous external floats
triggering the <a href="articles/float-bugs-1.html">IE Float Model</a>, as mentioned earlier.
</p>
<p>
Kudos to <a href="http://www.fu2k.org/alex/css/cssjunk/FloatInlineBlock.html">Alex Robinson</a>
for finding that inline-block is superior to the older inline-table fix for IE/Mac.
</p>
<h2>A Word Of Warning (this is important!)</h2>
<p>
The W3C float specification requires that a cleared element shall stay below <em>all previous floats</em>. There are no
exceptions to this requirement! "Previous" in this case means any float that comes earlier in the source document.
</p>
<p>
Up until November of 2004, Firefox was still incorrectly clearing only the floats that were vertically above the clearing element, rather
than all previous floats. This meant that in those earlier Gecko browsers you could place a floated column down one side of the
screen, and inside another column (possibly another floated column) you could clear a smaller interior float, <em>without that cleared
element dropping below the previous floated column</em>.
Since only Gecko had this problem, it was obvious that something was wrong every time this happened to a page. Normally Gecko is
the good browser, but in this one case it was the culprit. See, IE is not <em>always</em> the bad guy!
</p>
<p>
However, this easy clearing method has muddled the issue quite a bit, since now Explorer is not actually being cleared at all,
while Gecko browsers have finally been corrected so they do clear all previous floats.
</p>
<br />
<p>
...<em><strong>Oh no!</strong></em> Do you see what will now happen
in our hypothetical float page? IE, seeing no real clearing elements, will look great. Meanwhile, in newer
Gecko browsers and Opera 7, the CSS generated clearing element in the first easycleared box will drag the height of that box
waaaay down the page, until that invisible clearer is vertically below the bottom of the previous float column (assuming there
<em>is</em> a bottom!). This can "generate" a huge empty space inside that once-small easycleared box, depending on the actual
height of the neighboring float column.
</p>
<p>
Of course Opera 7 has always correctly implimented the clearing specs just like IE does (aside from bugs), and the Mac browsers
are not involved either. If you are wondering how this issue can be fixed, well, it can't. Gecko and Opera are now both following
the float clearing specs correctly, and IE only fails because of the faked "clearing" we are forcing upon it.
</p>
<h3>Preventing External Clearing</h3>
<p>
If you have the above described problem, one way to prevent the clearer from clearing the
adjacent float column is to make the container a float itself. Of course once you float the
container you no longer need easyclearing, sigh...
</p>
<p>
Note that when all the main elements in a column setup are floats, the worst IE
float bugs simply do not happen. Thus using an all-float approach to column design
can actually be easier to accomplish, at least within a rigid-width layout.
</p>
<h2>Them That Done It</h2>
<p>
<strong>Thanks</strong> to <strong>Tony Aslett</strong> for showing us the way.
His site, <a href="http://www.csscreator.com/"><strong>csscreator.com</strong></a>
is a killer CSS forum where newbies and gurus alike hang out and exchange CSS know-how. Tony's original
demo page for this method can be found <a href="http://www.csscreator.com/attributes/containedfloat.php">here</a>,
and the relevant forum thread is
<a href="http://www.csscreator.com/node/1667">here</a>.
</p>
<p>
Kudos also to <a href="http://dougsdvds.info/"><strong>Doug</strong></a> for pointing out the "period problem"
in FireFox, and to <a href="http://www.nolocation.com/"><strong>Mark Hadley</strong></a>
for that elegant IE/Mac fix, and to
<a href="http://www.loungepenguin.co.uk/indexno.htm"><strong>Matt Keogh</strong></a>
for showing how "inline-table" also fixes IE/Mac while using an already-approved
CSS property. Once more the CSS community comes thru for us all! :-)</p>
<br />
<p class="small alignright">
<a href="design/index.html"
title=" Big John's Advanced CSS Design "><strong>Big John Design</strong></a>
<a href="https://github.com/DerOperator/PositionIsEverything/issues">Contact Us</a>
©positioniseverything.net<br />
Last updated: July 2, 2008<br />
Created May 14, 2004
</p>
</div>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-39235363-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</body>
</html>