sganov

Both blending approaches have caveats: - **If the app optimizes for YOLO** by hiding its UI from autofill this would lead to suboptimal UX if there is no YOLO provider...

I totally agree that we should not give up the compatibility and we don't have to. Backwards compatibility is usually solved with a support library shims that are phased out...

If the autofill provider relies on data from the app manifest then it would change its behavior for entire app UI preventing autofill to handle data types Open YOLO does...

A solution is to hide the UI from autofill from the get go, query YOLO, and if no results force request an autofill. If the UI is not exposed we...