Before you update, please read the following

More Details about the TinyNav, just in case that anyone needs it:
http://themeid.com/help/discussion/4838/tinynav-1-8-7-update

Responsive Version 1.8.7 does not have many changes, however there is one change which may affect you if you are using header.php in your Child Theme and if you do not, please disregard.

1.8.7 now includes wp_title filter for better SEO visibility and overall Search Engine Ranking, this filter is highly recommended by WordPress as well as many SEO consultants.

How important is the page title you can read from here: http://www.seomoz.org/article/search-ranking-factors#metrics-6

What needs to be changed if you are using header.php in your Child Theme?

Open header.php from your Child Theme locate and replace the following:

Change:

<title><?php wp_title('&#124;', true, 'right'); ?><?php bloginfo('name'); ?></title>

To:

<title><?php wp_title('&#124;', true, 'right'); ?></title>

We are basically removing this:

<?php bloginfo('name'); ?>

because that is now handled by functions.php and or your favorite SEO Plugin, like All in One SEO, or WordPress SEO, whatever you choose to use.

Second part is Responsive Menu (TinyNav). As we noted in our changelog, TinyNav now has a "brother" and that is a SelectBox which will transform an old select box into something beautiful:

This is how closed menu looks like:



And when menu is opened:



Also note that menu will not close as soon as you mouseover, which is pretty great feature to have.

To take an advantage of new TinyMenu please locate your old .tinynav classes:

Change:

.tinynav {
        -moz-appearance: none;
        -webkit-appearance: none;
        -moz-border-radius: 2px;
        -moz-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        -webkit-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        -webkit-border-radius: 2px;
        appearance: none;
        background-color: #f9f9f9;
        background-image: -webkit-gradient(linear, left top, left bottom, from(#f9f9f9), to(#f1f1f1));
        background-image: -webkit-linear-gradient(top, #f9f9f9, #f1f1f1);
        background-image: -moz-linear-gradient(top, #f9f9f9, #f1f1f1);
        background-image: -ms-linear-gradient(top, #f9f9f9, #f1f1f1);
        background-image: -o-linear-gradient(top, #f9f9f9, #f1f1f1);
        background-image: linear-gradient(top, #f9f9f9, #f1f1f1);
        box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        border: 1px solid #ddd;
        border-radius: 2px;
        color: #333;
        display: block;
        filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=#f9f9f9, endColorstr=#f1f1f1);
        font-size: 12px;
        overflow: hidden;
        margin: 0 auto;
        padding: 4px 10px;
        text-shadow: none;
        width: 100%;
    }
    
    .tinynav:hover {
        -moz-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        -webkit-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        background-color: #fff;
        background-image: -webkit-gradient(linear, left top, left bottom, from(#fff), to(#f1f1f1));
        background-image: -webkit-linear-gradient(top, #fff, #f1f1f1);
        background-image: -moz-linear-gradient(top, #fff, #f1f1f1);
        background-image: -ms-linear-gradient(top, #fff, #f1f1f1);
        background-image: -o-linear-gradient(top, #fff, #f1f1f1);
        background-image: linear-gradient(top, #fff, #f1f1f1);
        border: 1px solid #ddd;
        box-shadow: 0 1px 0 rgba(255, 255, 255, 0.3) inset;
        color: #333;
        filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=#ffffff, endColorstr=#f1f1f1);
    }

To:

.tinynav {
        display: block;
    }
    
    .sb-holder {
        display: block;
    }

Let me also give you few more details. You will need to update TinyNav only if you're using a Child Theme and now the "Responsive" TinyNav stylings will no longer be in media queries, instead I moved them to the desktop area just so that we can address any future issues and/or improve Responsive navigations without asking you to change your Child Theme style.css. Think of it as an easier way to automate things.

The Changelog

Changelog Legend:

[+] = Added
[*] = Changed
[^] = Moved
[=] = No Changes
[x] = Deleted
[!] = Bugs

(02/06/2013) - Improvements - Version 1.8.7
[*] Copyright date change to 2013
[+] New and improved Responsive menu style updates in:
    - /js/responsive-scripts.js
    - /js/responsive-plugins.js
    - style.css
    - rtl.css    
[*] Language updates for:
    - responsive.pot
    - Italian
    - Dutch
    - Estonian
[+] SEO Improvements
    - Highly recommended wp_title filter added in functions.php
    -- http://codex.wordpress.org/Plugin_API/Filter_Reference/wp_title
    -- http://yoast.com/wordpress-themes-page-title/
[+] Unique function class for custom menus in widgets

If you have any questions, please don't hesitate to let us know and remember WordPress recommends Child Themes if you need to change anything in your Theme, I felt the need to remind you once again (well I'll keep on doing that in every release).

P.S. Do the changes one Theme is available for update. This is me giving you heads-up.

Complete changelog is always available:
http://themes.trac.wordpress.org/changeset?old_path=/responsive/1.8.6.1&new_path=/responsive/1.8.7

Quick Update: You can check new menu on http://themeid.com as well, I just did a live update on my main site, yes that's right, I always do that just for precaution if something breaks (even though changes are always well tested) let it break on my site. But, everything went great as usual.

And -or- http://themeid.com/responsive/?http://themeid.com/ in our Responsive Tool.

Thanks for using Responsive,
Emil Uzelac