Albertus Angga Raharja
Albertus Angga Raharja
@baskarap yes you are right, currently we support the `q` compression rate at Manipulator's constructor level, which results in constructing new Manipulator object for handling different `q` compression rate requests
:+1: to this, also encountering this bug on iOS 13
Hello, just want to share that my current workaround is using different package made by Baselow called [permission_handler](https://pub.dev/packages/permission_handler) which currently seem to return the correct permission status for location always.
+1, ```suggestion block with shortcut/button would be very helpful!
Following along this issue since I'd be interested to use this vscode extension as a tool for Chromium extensions development!
+1 on this issue, would be great to implement this feature!
I did something hacky related to this issue in `src/inspector/flutter/layout_explorer/flex/flex.dart:661` by removing `CrossAxisAlignment.baseline` from `CrossAxisAlignment` options because it will throw exceptions when `baseline` is null. If there are any additional...
@jacob314 because of the early design and decision on the scaling algorithm in Layout Explorer, we will always try to display and visualize a zero width/height on the Layout Explorer....