Today we released some updates to all of our customers on SDL Web (Tridion), updates that both help reduce page render time as well as eliminates errors when a page has been added into the system but your navigation component hasn't been published to reflect that change.  One of the more obvious improvements is both a visual and text indicator (for screen readers) of the current page you're on when using a mobile device.

When you open the mobile menu, the current page will be highlighted green with a black right chevron pointing to the page.  Persons with screen readers will be given the added text "(you are on this page)" next to the chevron and inline with that current menu item. If you do not see this on your website yet, you may need to clear your browser's cache.

In terms of performance improvements, we've changed how the menu is assembled on the client-side.  Now, when the navigation script evaluates your current URL against all of the menu items, it gracefully fails and looks for the nearest parental match in the navigation and reverse-builds out the left navigation from that nearest match.

Example:
Let's say your currently at this page:  http://mn.gov/agency/levelone/leveltwo/levelthree/levelfour/pageone.jsp — but you have a few situations that we have to deal with. For example, pageone.jsp is a new page and your navigation component hasn't been published yet.  Also, you forgot to make the structure group "levelfour" included in the navigation.  With those two situations, the left navigation would be reverse-built from "levelthree" on up.

Your menu might be something like this then:
Level One Main Structure Group 
 - Level Two Page/Structure Group
 - Level Two Page/Structure Group
 - Level Two Page/Structure Group
 - - Level Three Page/Structure Group
 - - Level Three Page/Structure Group

None of the level four items would show up because of the expected criteria:

• pageone.jsp was published but the navigation was NOT republished to include the new page,
• The "levelfour" structure group wasn't updated to display in navigation

The render time savings varied from page to page, but on average there was a 50% reduction in Finish time, DOMContentLoaded time, and overall load.  Not all pages saw a reduction in time, which may be due to other circumstances beyond our control — content issues or third party scripts that load beyond what point the navigation script finishes.  But in all, we've seen an improvement on render time.

You do not need to publish anything to receive this update.  All publications have received this change by publishing out the core.js file and your core.css page assemblies. 

Modified files:

• core.css (page assembly)
• layout.navigation.top.js
• layout.navigation.left.js
• layout.topnav.less