Describe the bug
When adding a bespoke toolbar (soho-toolbar-flex) above a datagrid, the size of the toolbar is not calculated correctly in all circumstances.
To Reproduce
Steps to reproduce the behavior:
ids-enterprise-ngflex-toolbar-datagridnpm run build:libnpm run starthttp://localhost:4200/ids-enterprise-ng-demo/toolbar-flex-datagridExpected behavior
Expect the toolbar to be of the correct height.
Version
Screenshots

Platform
Steps to Fix
@tmcconechy part of the issue here, is that we are trying to make the datagrid fill the available space, and also to ensure the scrollbars on the datagrid appear below the filter bar.
The issue appears the moment a parent div is added as follows:
<div class="full-height">
Yeah and that the flex-toolbar has height: 100%. cc @EdwardCoyle
The problem is that we need the height on the parent otherwise the scrollbars appear in unexpected places.
Also not sure why toolbar would have 100% height it could maybe have a fixed height like the old toolbar
Yes - the height: 100% is being added somewhere. I've committed the code to the branch now.
I also have a bit issue with that height 100% on toolbar flex but under other scenarios
My workaround (at this time) is to add the following:
<div soho-toolbar-flex style="height: auto;">
As far as the in-page context goes, I don't think the Flex Toolbar needs the height: 100%;. That rule is only necessary when the toolbar is contained by things like a Header or an expandable Contextual toolbar. It should be safe to remove.
So we should remove it in a PR then?
I'd say so, yes. It would involve:
Hi @tmcconechy. Tested in: http://master-enterprise.demo.design.infor.com/components/toolbar-flex/example-index.html
Noticed that the arrow down button doesn't show up when in responsive view.

Also, i there any way I can test #549
@janahintal What your seeing is normal. With flex toolbar we decided to just cut off the button if it does not fit. You just have to make the window wider if you want to see the whole button or live with it as is. This is the same as all previous versions.
Also you cant test #549 because its Angular so just moving to Done.