You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Gallery layout/size is not adjusted immediately anymore when resizing the browser window or rotating the smartphone.
Expected behavior
With nanogallery 2.4.2 the layout and thumbnail sizes for Mosaic and Cascading layouts were automatically adjusted while the window was being resized.
Nanogallery 3.0.1 does not do this anymore. The layout stays and pictures gets cropped (cf. screenshot) until one moves a scrollbar. Then the layout change is triggered and everything looks as it should.
A similar behaviour can be observed when viewing the page on a smartphone and the display is rotated.
=> 2.4.2 automatic adjustment of layout as soon as screen is rotated
=> 3.0.1 no adjustment of layout until scrolling up or down
Describe the bug
Gallery layout/size is not adjusted immediately anymore when resizing the browser window or rotating the smartphone.
Expected behavior
With nanogallery 2.4.2 the layout and thumbnail sizes for Mosaic and Cascading layouts were automatically adjusted while the window was being resized.
Nanogallery 3.0.1 does not do this anymore. The layout stays and pictures gets cropped (cf. screenshot) until one moves a scrollbar. Then the layout change is triggered and everything looks as it should.
I have added two JSfiddles an a screenshot to illustrate this:
Made with 3.0.1: https://jsfiddle.net/kfznvLyj/
Made with 2.4.2: https://jsfiddle.net/ujec5bqL/
Examples are made with
A similar behaviour can be observed when viewing the page on a smartphone and the display is rotated.
=> 2.4.2 automatic adjustment of layout as soon as screen is rotated
=> 3.0.1 no adjustment of layout until scrolling up or down
Tested:
Cascasing and Mosaic layouts
Win10: Firefox, Chrome, Edge
Android: Firefox
Any help is very much appreciated.
Cheers,
Alex
The text was updated successfully, but these errors were encountered: