Slava P.

@bosskmk Performance is always nice, but unfortunately features are selling point for customers :-( This particular one is quite important in many scenarios. In general it means an ability to...

@bosskmk Thank you

Actually --no-build does not work for integration tests, and situation is especially **BAD for Flutter Web**, because for Android there is working --use-application-binary flag. See https://github.com/flutter/flutter/issues/68529

yes, autofocus control as widget property is really needed.

I'm working on workaround for this issue - mostly concentrating on processing browser Back and browser address line manual changing. Looks like the key point for fixing them is AutoRouteInformationProvider.didPushRouteInformation()...

@komakur I've fixed that problem. You may check it out and let me know if it works for you. Unfortunately, it is impossible to extend AutoRouteInformationProvider, so I have to...

@komakur Have you modified your AppRouter? ```dart class AppRouter extends $AppRouter { AppRouter({super.navigatorKey}); AutoRouteInformationProviderEx? _lazyInformationProvider; /// Builds a lazy instance of [AutoRouteInformationProviderEx] @override AutoRouteInformationProviderEx routeInfoProvider({ RouteInformation? initialRouteInformation, bool Function(String? location)?...

New semi-duplicate issue about that: https://github.com/Milad-Akarie/auto_route_library/issues/1825 I've added a workaround code there.

Instead of deprecating HTML renderer - assign resources to improve it (Google is not poor and can afford to hire five additional developers). It has to be more configurable than...

@yjbanov _Unfortunately, the HTML renderer does not present a good case here._ I strongly don't agree with that statement - having a "customizable" html renderer could solve multiple problems. It...