Issue Description

Method Future<LatLng> getLatLng(ScreenCoordinate screenCoordinate) returns different results for the same ScreenCoordinate on iOS and Android.

Steps to Reproduce

1. Add GoogleMap widget filling entire device screen.
2. Set initialCameraPosition.target to (lat; lng) coordinates.
3. Retrieve GoogleMapController in onMapCreated handler.
4. In onCameraIdle

Select component's onChange is work, but it cannot render selected value.

import React, { useState } from 'react';
import InputLabel from '@material-ui/core/InputLabel';
import Select from '@material-ui/core/Select';
import MenuItem from '@material-ui/core/MenuItem';

export default function Test() {
  const [test, setTest] = useState({
    a: '',
    b: '',
    sum: {

Tabs in cards are not working in new v.1.0.0.

I have tested on starter template.

Let me know if you need further information.

Thanks for your help.

In the section titled "CAN I BUILD OR USE INDIVIDUAL MDL COMPONENTS (E.G A BUTTON)?", there are two broken links: https://getmdl.io/faq/index.html#individual-components

Environment

Vuetify Version: 2.0.5
Vue Version: 2.6.10
Browsers: Chrome 76.0.3809.100
OS: Windows 7

Steps to reproduce

View it in mobile to see the "test" column spill into the next row

Expected Behavior

Overflow to be hidden or expand row

Actual Behavior

Overflows into the next row

Reproduction Link

<a href="https://codepen.io/teellcory/pen/

Test Case

https://codepen.io/valendres/pen/NzqyqN

Summary

Using @extend inside a ::before or ::after pseudo selector can result in invalid css, causing styling to not be applied to target elements. This happens when attempting to apply styling to elements within a .btn

Expected result

To be able to apply css on specific elements within a .btn.

Additional Informa

Bug, enhancement request, or proposal:

In mat-form-field with outline appearance you can insert a mat-chip-list inside the form-field but the label doesn't go above the input
it's look like a bug, because if we insert the mat-chip-list outside or if we change the appearance everything look good

![Capture d’écran 2019-06-13 à 11 20 54](https://user-images.githubusercontent.com/1983788/59420

There are a lot of demos (e.g. https://material-components.github.io/material-components-web-catalog/#/component/menu). It would be really helpful if the demos included the source code for what is being demonstrated. Right now, it's like "here's what you can do, and here's the link to the entire component so you can tediously go figure out how it was done" :)

This feature allows you search a page directly by just typing its URL and "TAB" key. It works on Quasar forum for example (but also on YouTube, Facebook, StackOverflow etc.).

This would be very handy, because you can skip two steps when looking up a docs page.

What we need to do to achieve this:

1. Sync search input with URL query (or route param, but query is probably easier with current

Not a single form field has a label. These designs are not usable and the patterns presented should be discouraged.

I suggest adding a validation check like Nu Validator, aXe, lighthouse, etc. to show all the places this markup is invalid.

Is there any way to implement horizontal radio button group?

Some suggestions to improve the documentation of bootstrapTable:

• column option "sorter": please include expected return values for custom sorter function (it was only through guessing that I found out it's actually -1, 0, 1)
• table options/column options/events/methods: please sort the options/methods in alphabetical order - also in the index in the right column (it's very tedious to scan f

The Input component defines an input tag along with a role attribute equal to 'input'. This causes some accessibility scanners to raise the following violation:

"The WAI-ARIA role(s) and/or attribute(s) input are not valid for the element input"

Is there a way we can remove the redundant role or at least provide a way to override the value?

You can use Cypress plus cypress-vue-unit-test to test single file components (.vue files) that you create. If your components have been built with vue-material then you need it to be available during test so that your component under test loads correctly. I have found the following template to be effective and it coul