“List Tools” tab is no longer available after addi

问题:

in SharePoint 2010 I have added my webpart above list (standard list or documents library list - it doesn't matter). After this "List Tools" tab is not visible. After some digging I have found, that problem exists even if I add one of the standard SharePoint WebParts.

Here is the same problem and description how to reproduce it: http://www.endusersharepoint.com/STP/viewtopic.php?f=10&t=2027

Has anybody found the solution or real workaround for this?

//EDIT: I've found a "solution". Ribbon is connected with "actual" webpart. One click on the list (to set the focus on it) and the tab is visible again :D

回答1:

When you add a web part to the standard list views, the page is no longer classified as a list view page, but instead it is classed as an application page.

This means you lose the ribbon menu, as well as the view selector in the breadcrumb.

UPDATE

You can see the code that hides the view selector in:

Microsoft.SharePoint.WebControls.ListTitleViewSelectorMenu.SingleWebPartPresentOnPage

But I can't seem to find the code that hides the ribbon.

UPDATE

Okay i think this will work, add a content editor web part with this code:

<script>
setTimeout(function() {
    var elem = document.getElementById("MSOZoneCell_WebPartWPQ2");
    if(elem != null) {
        var dummyevent = new Array();
        dummyevent["target"] = elem;
        dummyevent["srcElement"] = elem;
        WpClick(dummyevent);
    }
}, 2000);
</script>

Replace the MSOZoneCell_WebPartWPQ2 id with the web part zone cell of the list view web part.

回答2:

This worked for me, but it starts with the documents tab selected, and I preferred to have the default browse tab selected to begin with, so I just added a simple line to the code, do reselect the default tab:

        <script>
        setTimeout(function() {
        var elem = document.getElementById("MSOZoneCell_WebPartWPQ2");
           if(elem != null) {
                var dummyevent = new Array();
                dummyevent["target"] = elem;
                dummyevent["srcElement"] = elem;
                WpClick(dummyevent);
                _ribbonStartInit("Ribbon.Browse", true)
            }
        }, 2000);
        </script> 

回答3:

After a ton of stepping through the SharePoint JS in a debugger, I've finally found a way to prevent this problem.

In SharePoint 2010:

//Set focus on our list web part
var webPart = document.getElementById('WebPartWPQ1');
WpClick({target: webPart});

//Prevent it from losing focus
SP.Ribbon.WebPartComponent.$3_1.deselectWebPartAndZone = function() { };

In SharePoint 2013 Beta:

//Set focus on our list web part
var webPart = document.getElementById('MSOZoneCell_WebPartWPQ2');
WpClick({target: webPart});

//Prevent it from losing focus
SP.Ribbon.WebPartComponent.$3.deselectWebPartAndZone = function() { };  

Note: This is super-hacky, and is in no way supported by Microsoft (thus it's very likely to change in a future version or possibly even the RTM of SharePoint 2013).

Also, note that your web part ids are likely to be different, so you should double check you're giving focus to the correct web part.

Explanation: It basically overrides the instance of SP.Ribbon.WebPartComponent's ability to deselect a web part. From what I can tell, the $3/$3_1 property stores a reference to the SP.Ribbon.WebPartComponent instance.

If anyone knows of a better way to access the instance of SP.Ribbon.WebPartComponent other than the $3/$3_1 property, please speak up, as that would be make this method much more robust.

回答4:

Clicking on the list (setting focus on it) solved the "problem" ;)