Community @ The Turning Gate

True, but then you would have to replace it with some other way of indicating the touch event.

I don't claim to be an expert in javascript by any means, but I looked through the scripts and didn't find anything that would explain it either. I also tried inspecting it (simulating a mobile browser) with javascript disabled, and it was still happening.

I actually have this:

#nav span a, 
#nav span a:hover, 
#nav > span:first-child > a, 
#nav li a, 
#nav li a:hover, 
#nav li span, 
#nav li li a, 
#nav li li span,  
#nav > li:first-child > a,
#nav a:hover
    {
    -moz-border-radius: 0px;
    -webkit-border-radius: 0px;
    border-radius: 0px;
    }
}

in my custom css. I even tried changing those values in the actual navigation.css file to see if the custom css just wasn't taking hold in that case. I can't find anywhere in any of the css files that would be causing the change.
Thanks,
Kyle

This is a much cleaner way of doing the same thing. This leaves the original search intact, and just hides the unwanted information, as opposed to overwriting the whole search page. With this function, the search term stays in the search bar, and you get a message for 'no photos found'.

function ttg_block_bottom( $style, $path ) {
    if (G_PATH == 'SEARCH') {    
        echo '
        <script>
        (function(){
            if(document.getElementById("content")!=undefined){            
                if(document.getElementById("content").innerHTML.indexOf("criteria")>-1){
                    document.getElementById("content").innerHTML="<p><cite>No photos matched your search criteria</cite></p>";
                } else {
                    document.getElementById("content").style.display="none";
                }
            }
        })();
        </script>
        ';
    }
} // END

I modified my search page to hide the album search using PHPlugins to replace the block. Here is my function if you are interested:

function ttg_block_top( $style, $path ) {
    if (G_PATH == 'SEARCH') {
        echo '
        <div id="primary-content" class="container_12 collapse clearfix">
        <div id="search" class="collapse clearfix">
        <h2>Search</h2>
        <hr />
        <form action="./" method="GET">
        <input type="text" id="q" name="q" value=""/>
        <button type="submit">Search</button>
        </form>
        </div> <!-- #search -->
        </div>
        ';
        return false; 
    }
    return true;
} // END

You can take a look here (try searching for 'Nassau'). I also increased the max width via custom css:

#search {
    max-width: 1140px;
    }

I had just tried it in Chrome and Firefox. I actually just figured out what it is. I use an ad blocker in both browsers, and for some reason it was picking up on the share icons... I disabled it for my domain, and everything is working again. Thanks for taking a look.

Markdown doesn't process inside block-level HTML tags. You will have to use the HTML tags instead.

Source: http://daringfireball.net/projects/markdown/syntax#html

You might also want to try writing the content in a Markdown editor, as opposed to directly in Lightroom. That will let you see the changes as you write it, and before you publish. Matt has some recommendations in the docs.

Glad to help!

You are coming up with some great (and original) ways to use 20/20. Very impressive!

You have some beautiful images. And I really like the design of your site. Great job!