This has indeed changed in 2017r2 - I have some small scripts that manipulate the output of a menu proxy using $(document).ready() like you and find that jquery scripts are executing before the new MadCap JS that dynamically generates parts of the page.
In this new release the menu proxies (and perhaps your home button) are no longer static elements in the page, rather they are generated by MadCap's JS and inserted on the fly. I'm not sure in which order they execute, but it's after document.ready(), so any old scripts now execute before the elements they should work upon exist.
For instance, instead of a full list with li's and links, in the source of my page my TOC now looks like:
Code: Select all
<ul class="nocontent menu mc-component" data-mc-linked-toc="Data/Tocs/ByModule__Reporting.js" data-mc-side-menu="True" data-mc-max-depth="2" data-mc-include-icon="False" data-mc-include-indicator="False" data-mc-include-children="True" data-mc-include-siblings="True" data-mc-include-parent="False" data-mc-toc="True">
</ul>
so my code changing the list items has no effect because when it is executed they do not yet exist.
I would suggest you use CSS to hide your element as that will apply to any dynamically-generated elements when they are created.
If anyone else knows how I can delay my jquery script to work after Flare's new javascript runs that would be great...