Angular2 based Material Design components, directives and services are Accordion, Autocomplete, Collapse, Colorpicker, Datepicker, Dialog(Modal), Menu, Multiselect, Select, Tabs, Tags(Chips), Toast and Tooltip.
When a resize occurs that restricts the visibility of the tabs which is not a window resize, the arrows visibility do not update.
What is the expected behavior?
Ideally checking if the arrows should be displayed for tab navigation should be based on a resize of the components size, not the windows size. A windows size can stay the same and something inside the page can occur to shrink the element,
What is the current behavior?
If no window resize occurs, the arrows visibility do not update
Adjust the screen size so that the tabs are bouncing all the way in and partially 'out' of the page. (Notice how no arrows are being rendered to compensate for the smaller space)
Drag the middle bar that separates the code from the rendered application while the tabs component is partially 'off' the page. If done correctly the arrows should have begun to render.
What is the use-case or motivation for changing an existing behavior?
Annoying
Which versions of Angular, MD2, OS, browsers are affected?
Bug, ~feature request, or proposal~:
When a resize occurs that restricts the visibility of the tabs which is not a window resize, the arrows visibility do not update.
What is the expected behavior?
Ideally checking if the arrows should be displayed for tab navigation should be based on a resize of the components size, not the windows size. A windows size can stay the same and something inside the page can occur to shrink the element,
What is the current behavior?
If no window resize occurs, the arrows visibility do not update
What are the steps to reproduce?
http://plnkr.co/edit/35SFbMJYetvCnYD6bkRY?p=preview
What is the use-case or motivation for changing an existing behavior?
Annoying
Which versions of Angular, MD2, OS, browsers are affected?
Current version of MD2
Is there anything else we should know?