Ray Li

Thanks for filing this issue. I've noticed that there are quite a few Cupertino related bugs. Cupertino support is planned for v0.3.0. However, this specific issue might be fixed when...

Context for the original conversation: #33 > What do you think about the idea of removing breakpoints and instead have breakpoint segments that allow you to control the behavior instead?...

The syntax for breakpoints would change to something like this: > ResponsiveBreakpoint(start: 0, end: 420, behavior: ResponsiveBehavior.autoscale, platform: [Platform.android, Platform.iOS], tag: "MOBILE_SMALL", orientation: [Orientation.landscape]);

Thanks for reporting this issue. Can you provide a sample code of your dropdown button? There are a few known issues with modals and routes that are on the roadmap...

I've done a bit of research into Overlays and there's hope for a good solution.

You might have caught an edge case here. Looks like if a breakpoint is set to minWidth, then the minWidth overrides the breakpoint name?

Let me check the tests and see what's going one. Meanwhile, you can change the mobile breakpoint from 450 to 451 px.

Thank you for reporting.

Hmmm, this is on the v0.2.0 release roadmap. Any ideas how to fix the issue?

Thanks for reporting this issue. I'm going to look into if it is possible to overwrite the root level MediaQuery parameters. Some framework widgets fetch their layout from the root...