Differences between SharePoint’s Oslo and Seattle master pages

If you’ve been looking at the neat new masterpages with SharePoint 2013, and playing around with changing them, you can quite easily see a difference between the two options: Oslo and Seattle. Seattle is what we’re used to with SharePoint 2010: left nav and a top nav. Oslo moves the left nav to the top, and removes the top nav all together. Oslo also provides more room for your content by widening the area by moving the left nav.

SharePoint's Oslo Masterpage

Oslo Masterpage Layout

SharePoint's Seattle Masterpage

Seattle Masterpage Layout

But what is really different, technically speaking? I compared the two pages and found a little more:

Comparing Oslo to Seattle Master Pages

  • Oslo uses a different CSS, obviously, oslo.css instead of corev15.css. Also, the CSS link has EnableCssTheming set to true, whereas Seattle doens’t state anything.
  • Oslo has several accessibility and animation links wrapped with a SPSecurityTrimmedControl, configured to hide the contents from the search crawler. Seattle just has the links listed, no security trimming.
  • Oslo has a AuthenticatedUserDiv tag wrapping almost all of the content on the page. This control “Renders a DIV element which has different styles based on whether the current user is authenticated or anonymous” (from MSDN article). This control is configured with an authenticated style set to a CSS class. So when an authenticated user accesses the site, it uses a CSS class, when it’s anonymous, no class is specified at all.
  • Oslo has several other areas and controls wrapped with SPSecurityTrimmedControl configured to restrict to authenticated users only.
  • Oslo has a couple of small areas where CSS class names differ.
  • There’s the obvious changes with the navigation and header, and previously noted.
  • The PlaceHolderTopNavBar content place holder is thrown at the bottom of the page, and is set to be hidden. So that’s where that went.

Seeing there are a lot of security trimming around authenticated vs anonymous, I decided to test that out to see what it looks like.

First, let’s see what Seattle looks like anonymously:

SharePoint Seattle Masterpage in Anonymous

Interesting, the web parts are intelligent enough to know anonymous users can’t “get started” and the newsfeed is gone. Also, some of the ribbon items change. Nothing else too significant.

Next up, Oslo:

SharePoint Seattle Masterpage in Anonymous

Whoa, that’s a lot more now isn’t it? We lost the ribbon completely, including the SharePoint blue bar at the top. It feels naked.

I compared the HTML output of the two sets of pages as well.

  • Seattle didn’t differ much, minor items, but nothing too specific to anonymous vs authenticated.
  • Oslo, huge differences, entire sections are missing. Those security trimmed sections I mentioned before, poof, gone.

It almost feels like Oslo was designed with anonymous access in mind, as in Microsoft wanted us to use Oslo for public facing sites, as it took care of so much for you already. 😉

Article from: http://davidlozzi.com/2013/09/25/theres-more-than-meets-the-eye-differences-between-sharepoints-oslo-and-seattle-master-pages/

SharePoint 2013 Provides several Out of the box master pages to fulfill different business requirement.
In Seattle and Oslo master pages the Only difference in their page layout and navigation.
Seattle is what we have been using from SharePoint 2010, and Oslo is new.

Seattle:

  1.  Seattle is designed for intranet team collaboration portal with more features such as  social, content\site navigation and management,etc.
  2. There is a Left navigation is exist and we can set Top navigation for top level sites and sub sites.

seattle

Oslo:

  1.  Oslo master page is designed for publishing site which focus on page layout and content rendering.
  2. moving the left navigation to the top, and removing the top navigation all together. Oslo has a wider layout for your content.oslo