Premium support for our pure JavaScript UI components


Post by damir »

When enabling autoHeight with one row inside gantt, then the splitter button is hidden behind the header.

I was able to reproduce this in your demo, but just by adding the b-autoheight class to .b-grid-panel-body

Find on attachment the screenshot of my setup and your demo.

Thanks

Screenshot 2024-03-14 125501.png
Screenshot 2024-03-14 125501.png (136.25 KiB) Viewed 265 times
Screenshot 2024-03-14 125341.png
Screenshot 2024-03-14 125341.png (15.71 KiB) Viewed 265 times

Post by alex.l »

Hi damir,

Am I right to reproduce a bug you need to manually change classes in DOM?
I am afraid we can't confirm this as a bug. Could you pls provide a code to reproduce this?

All the best,
Alex


Post by damir »

I see that the prop autoHeight add that class in DOM.
I can't see how to edit your react demo, and when adding autoHeight config in vanilla JS demo here https://bryntum.com/products/gantt/examples/basic/ nothing happen.

Do you have a demo where I can see autoHeight working?

Thanks


Post by alex.l »

Hi damir,

You can find source code for all our demos in sources you downloaded from CustomerZone. Just check /examples/frameworks/react folder.

Apply required changes to reproduce the problem and attach an app here.

All the best,
Alex


Post by damir »

Yes I know but recently I have an issue running npm install, I think is some security policy added recently by my company.
The postinstall script seems not working:

npm ERR! code 9
npm ERR! path C:\Users\dgrgic\Downloads\bryntum-gantt-5.6.6\gantt-5.6.6\examples\frameworks\react\typescript\basic\node_modules\core-js-pure
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node -e "try{require('./postinstall')}catch(e){}"
npm ERR! node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
Last edited by damir on Thu Mar 14, 2024 4:20 pm, edited 1 time in total.

Post by damir »

will try to sort out this in case you know another way to solve this


Post by damir »

even removing postinstall scripts from package.json give the same error.


Post by tasnim »

Hi,

Please try removing the node_modules and package-lock.json folder and try npm i again. Does that help?


Post by damir »

there is not the node_modules and package-lock.json since I download last version I was never able to install. and when error happen, nothing is installed, so there is not node_modules.

Screenshot 2024-03-15 090222.png
Screenshot 2024-03-15 090222.png (305.83 KiB) Viewed 201 times

Post by alex.l »

All the best,
Alex


Post Reply