fix(data-iterable): rows-per-page selector not inheriting theme

[jacekkarczmarczyk]

Motivation and Context

Iterable's rows-per-page selector takes the theme from the app instead of the component (data-iterable, data-table)

https://codepen.io/anon/pen/pOBLaO

How Has This Been Tested?

visually

Markup:

<template>
  <v-app :dark="dark">
    <v-content>
      <v-container>
        <v-switch label="Dark" v-model="dark"></v-switch>
        <div class="headline mt-5">No theme</div>
        <v-data-table :headers="headers" :items="desserts">
          <template slot="items" slot-scope="props">
            <td><v-edit-dialog>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
            <td><v-edit-dialog large>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
          </template>
        </v-data-table>
        <div class="headline mt-5">Dark</div>
        <v-data-table dark :headers="headers" :items="desserts">
          <template slot="items" slot-scope="props">
            <td><v-edit-dialog>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
            <td><v-edit-dialog large>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
          </template>
        </v-data-table>
        <div class="headline mt-5">Light</div>
        <v-data-table light :headers="headers" :items="desserts">
          <template slot="items" slot-scope="props">
            <td><v-edit-dialog>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
            <td><v-edit-dialog large>Click<v-text-field slot="input"></v-text-field></v-edit-dialog></td>
          </template>
        </v-data-table>
      </v-container>
    </v-content>
  </v-app>
</template>

<script>
export default {
  data() {
    return {
      dark: false,
      headers: [
        { text: "Dessert (100g serving)", value: "name" },
        { text: "Iron (%)", value: "iron" }
      ],
      desserts: [{
        value: false,
        name: "Frozen Yogurt",
        iron: "1%"
      }]
    };
  }
};
</script>

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement/refactoring (non-breaking change that doesn't add any feature but make things better)

Checklist:

• The PR title is no longer than 64 characters.
• The PR is submitted to the correct branch (master for bug fixes, dev for new features and breaking changes).
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have created a PR in the documentation with the necessary changes.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord