Allow snippets windows to be resized.
The "Sample Code" windows leave a lot of empty space, and sometimes I want to expand the window to read the code better.
Being able to click and drag to accomplish a resize like this would be very helpful:

This is especially pertinent with the Flutter dartpad integration (issue link).
A little more detail from DartPad-land -- we just integrated DartPad into the AppBar widget:
https://master-api.flutter.dev/flutter/material/AppBar-class.html
The width of the editor is definitely pretty tight, and adjusting the column layout to let it expand rightwards would provide a better experience. I wanted to do this when I added the snippet generator for DartPad, but didn't have enough working knowledge of the CSS in place to attempt it.
I'm not sure where you all fell on this issue, but I found that hiding the right sidebar and shrinking the font on code pages made for a more ergonomic experience when reading the docs. Let me know if there is any way I could contribute to make this happen.
Without modifications:

With right sidebar hidden and smaller code font:

It is "technically" now possible to resize dartpad iframes (only vertically) on website. But even that is not working properly.
I can see a "resize" css attribute is used:
But its not holdable or dragable and on hovering mouse it doesn't even change the mouse pointer to indicate any action is possible. This happens in chrome and edge both.
In firefox, it doesn't display resize icon at all.
This specific issue seems to be for api.flutter.dev where DartPad is also embedded. There have been a few improvements here:
- DartPad in api.flutter.dev uses a new embed layout with much less UI chrome, increasing space for the embedded DartPad.
- On narrow layouts, DartPad will instead switch to a tab-based layout allowing you to focus either the code or the output.
- api.flutter.dev added an override style allowing the content to take up the full page width, which results in the mentioned cases being much much wider.
I hope for now this results in a slightly improved experience, but if anyone still has new or existing issues, please open a new issue with updated context. Thanks!