Fixed
Status Update
Comments
je...@google.com <je...@google.com>
lu...@google.com <lu...@google.com>
an...@google.com <an...@google.com> #2
Thanks for filing Alex. Not handling it at all would be a burden for developers to handle IMO, as it will be hard to guess what sides are handled by top/bottom app bars and what should be handled by the content manually. It is probably better than claiming all the padding automatically, I agree.
Would this make sense for scaffold to handle and consume the insets on the sides where we have top and bottom app bar, so that the rest is handled by the application? Still not ideal, but at least it is easier to wire up when nesting is involved.
Description
Create a fused library but don't provide namespace. Build it.
Error:
This looks like an internal error. We should have a proper check that tells developers exactly what to do.