+ Keyboard Navigation uses CSS Selectors to find the hyperlinks on the page that define the previous and next links on the page,', 'keyboard-navigation') ?>
+
+
+
+
+
+
+
+
+
+
+
+
+ a#next-link
+
+
+
+
+
+
+
+ div.nav div#next-link-holder a
+
+
+
+
+
+
+ Keyboard Navigation extends this slightly so that, if the target element is not a <a href> tag,', 'keyboard-navigation') ?>
+
+
+
+
+
+
+
+
+
+
+
+ nth-child:', 'keyboard-navigation') ?>
+
+ div#menunav a:nth-child(2)
+
+
+
+ Keyboard Navigation will move up through the DOM tree until it finds <a href="next-page">:', 'keyboard-navigation') ?>
+
+ div#menunav a span.next
+
+
+
+
+
+
+
+
+ Keyboard Navigation requires that the visitor have JavaScript enabled. This plugin uses', 'keyboard-navigation') ?>
+
+ load their own copies of the Prototype library, both plugins will break.', 'keyboard-navigation') ?>
+
Are you a theme author? Send your theme's navigation defaults to John Bintz and get them included!
-
-
-
-
How does this work?
-
Keyboard Navigation uses CSS3 Selectors to find the hyperlinks on the page that define the previous and next links on the page, and then uses JavaScript to assign the act of hitting the left and right arrow keys on the keyboard to clicking those links. This is exactly the same approach that you would use to style a specific element on the page:
-
-
-
-
-
Targeting the <a href="next-page"> on this page is quite easy — provide the CSS selector for the id of the element:
-
-
- a#next-link
-
-
-
If the <a href> does not have an id, but does have a class, or is the only child of a particular element, you can use syntax like:
-
-
- div.nav div#next-link-holder a
-
-
-
-
-
Keyboard Navigation extends this slightly so that, if the target element is not a <a href> tag, Keyboard Navigation will move up through the tree from the found element until an <a href> is found:
-
-
-
-
-
You have two approaches for identifying the <a href="next-page"> tag:
-
-
Using CSS3 selectors, you can use nth-child:
-
- div#menunav a:nth-child(2)
-
-
-
Using more familiar CSS syntax, target the <span class="next"> element, and Keyboard Navigation will move up through the DOM tree until it finds <a href="next-page">:
-
- div#menunav a span.next
-
-
-
-
-
-
-
Keyboard Navigation requires that the visitor have JavaScript enabled. This plugin uses
- the Prototype JavaScript library, and including it will increase the size of your total site download. Additionally,
- if other plugins load their own copies of the Prototype library, both plugins will break.
-
-
\ No newline at end of file
diff --git a/styles.css b/styles.css
index 08fc114..0e2102d 100644
--- a/styles.css
+++ b/styles.css
@@ -7,10 +7,8 @@ div.image-holder {
overflow: hidden
}
-div.image-holder div {
- float: left;
- display: inline;
- width: 440px;
+div.image-holder div p {
+ margin-top: 0
}
div.image-holder img {
@@ -24,30 +22,32 @@ div#top-holder {
}
div#top-holder form {
- float: left;
- display: inline;
- width: 650px;
+ margin-right: 300px
+}
+
+div#top-holder th {
+ padding-left: 0
}
div#top-holder form input[type="text"] {
- width: 440px
+ width: 100%
}
-div#top-holder form input[type="submit"] {
- width: 250px
-}
-
-div#top-holder div {
- float: left;
+div#top-information {
+ float: right;
display: inline;
- width: 295px;
+ width: 270px;
border: solid #ddd 1px;
- margin-left: 10px;
- margin-top: 10px;
padding: 10px;
background: #dfe
}
div#top-holder div p {
margin-top: 0
-}
\ No newline at end of file
+}
+
+div#top-holder .form-table {
+ clear: none
+}
+
+.clear { clear: both }
\ No newline at end of file
diff --git a/wordpress_pathfinding.php b/wordpress_pathfinding.php
deleted file mode 100644
index 69eb990..0000000
--- a/wordpress_pathfinding.php
+++ /dev/null
@@ -1,24 +0,0 @@
-domain . $site->path);
- } else {
- return get_option('home');
- }
-}
-
-function pathfinding_get_admin_url() {
- if (function_exists('get_current_site')) { // WPMU
- return cpm_get_home_url();
- } else {
- return get_option('siteurl');
- }
-}
-
-function pathfinding_get_plugin_path() {
- return (defined("MUPLUGINDIR") ? MUPLUGINDIR : PLUGINDIR) . '/' . preg_replace('#^.*/([^\/]*)#', '\\1', dirname(plugin_basename(__FILE__)));
-}
-
-?>
\ No newline at end of file