[SalesForce] Remove buttons from Listview in VisualForce Page

When you're in Lightning Experience, you should rely on sforce.one to manage navigation for you. Not only navigation will work, but also navigation history will be saved correctly.

Unfortunately, sforce.one isn't available in Salesforce Classic, so if your Visualforce page needs to be exposed both on Lightning Experience and Salesforce Classic, you'll need to create a function to handle both cases.

For instance, if you want to create a button that redirect you to an Account creation page, you can do something like this:

function createAccount() {
    if ((typeof sforce != 'undefined') && sforce && (!!sforce.one)) {
        // Manage navigation in Lightning Experience & Salesforce1
        sforce.one.createRecord('Account');
    }
    else {
        // Manage navigation in Salesforce Classic
        window.top.location = '{!URLFOR($Action.Account.New)}';
    }
}

Then, you'll need to call this function on your button:
<apex:commandButton onclick="createAccount();" value="Navigate"/>

You can have a look to sforce.one documentation for your other use cases (display a record, edit one...): https://developer.salesforce.com/docs/atlas.en-us.salesforce1.meta/salesforce1/salesforce1_dev_jsapi_sforce_one.htm

Also, there is a Trailhead about Lightning Experience and Visualforce, with a specific focus on navigation. https://developer.salesforce.com/trailhead/lex_dev/lex_dev_visualforce/lex_dev_visualforce_navigation I encourage you to have a look to the whole module.

It is a common assumption that the HTML to PDF engine presently used by Salesforce is Flying Saucer that only supports version 2.1 of CSS (W3C Recommendation 07 June 2011) whereas SLDS is designed to work with modern browsers only that support version 3 CSS.

So while you may be able to eventually get some parts of the SLDS markup to work, the PDF output is unlikely ever to be as you would like it to be. Including simple CSS used just for the PDF output is the simplest workaround.