This is the respective issue as Create new “Views Responsive Grid” format for Views Core
I know that we have implemented #479 many years ago, and that we also have issues like #4375 and #4560, but I just came across this: Views Responsive Grid added to Drupal 10 core article, and it seems to me that what our Drupal brethren have implemented would work better and more intuitively:
Earlier today a new killer feature was committed to Drupal 10 core: Views Responsive Grids. But, it’s more than that. ... The styles make use of new modern CSS that enable super cool features.
Instead of specifying the number of columns, and screen widths, we specify:
- the maximum number of columns, and
- the minimum grid cell width.
- the gutter spacing
This is way more flexible than the former method!
The CSS works in such a way that when the grid cells resize to a point where they’re below the minimum width, the grid will reflow to have less columns. Alternatively, the grid will expand to fit in as many columns as permitted, while keeping the grid width above the minimum value!
Also, because the CSS is not reliant on the viewport width, the same grid view display is able to be used in a large region (and show more columns) and a narrow region (which would show less columns)! It will adjust automagically!
...
Here it is in action:


https://herchel.com/sites/default/files/2022-08/grid-view.mp4
One thing to consider is that such a feature would not work with IE11. ...but is that even an issue nowadays, with most of the world using either Chrome or Edge?
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists