(In reply to Daniel Holbert [:dholbert] from comment #2) > The network track shows that we make a connection to `http://rbi.org.in/` despite the fact that I typed `rbi.org.in` into my URLbar (schemeless) which should make it automatically choose https as the protocol. This is more or less expected, as schemeless HTTPS-First was only intended to ship on Desktop. We should have probably documented that better. (In reply to Daniel Holbert [:dholbert] from comment #4) > Bit of a shot-in-the-dark, but I'm guessing this commit from bug 1812192 [...] needs some equivalent logic for the Fenix URLbar code, to set `wasSchemelessInput` as-needed for user-entered URLs. Yes, that sounds about right if we wanted to ship schemeless HTTPS-First on Android as well. But as the current plan is to ship full HTTPS-First (Bug 1921221), like was already done in Nightly, I am not sure if we should focus our efforts on bringing schemeless HTTPS-First to Android first. But on the other hand, we are currently also discussing using `wasSchemelessInput` to decide when we should **not** do a regular HTTPS-First upgrade (Bug 1919544). Considering that, I think we should actually do work on setting `wasSchemelessInput` correctly on Android. I am not sure if this is something the Android team wants to work on. If not, I can also try to set up an Android environment and work on this, but that may take a bit longer than if somebody already experienced with the native android address bar code does it.
Bug 1901120 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Daniel Holbert [:dholbert] from comment #2) > The network track shows that we make a connection to `http://rbi.org.in/` despite the fact that I typed `rbi.org.in` into my URLbar (schemeless) which should make it automatically choose https as the protocol. This is more or less expected, as schemeless HTTPS-First was only intended to ship on Desktop. We should have probably documented that better. (In reply to Daniel Holbert [:dholbert] from comment #4) > Bit of a shot-in-the-dark, but I'm guessing this commit from bug 1812192 [...] needs some equivalent logic for the Fenix URLbar code, to set `wasSchemelessInput` as-needed for user-entered URLs. Yes, that sounds about right if we wanted to ship schemeless HTTPS-First on Android as well. But as the current plan is to ship full HTTPS-First (Bug 1921221), like was already done in Nightly, I am not sure if we should focus our efforts on bringing schemeless HTTPS-First to Android first. But on the other hand, we are currently also discussing using `wasSchemelessInput` to decide when we should **not** do a regular HTTPS-First upgrade (Bug 1919544). Considering that, I think we should actually do work on setting `wasSchemelessInput` correctly on Android. ~~I am not sure if this is something the Android team wants to work on. If not, I can also try to set up an Android environment and work on this, but that may take a bit longer than if somebody already experienced with the native android address bar code does it.~~ Ah, I just saw that Sunil already has assigned this himself.
(In reply to Daniel Holbert [:dholbert] from comment #2) > The network track shows that we make a connection to `http://rbi.org.in/` despite the fact that I typed `rbi.org.in` into my URLbar (schemeless) which should make it automatically choose https as the protocol. This is more or less expected, as schemeless HTTPS-First was only intended to ship on Desktop. We should have probably documented that better. (In reply to Daniel Holbert [:dholbert] from comment #4) > Bit of a shot-in-the-dark, but I'm guessing this commit from bug 1812192 [...] needs some equivalent logic for the Fenix URLbar code, to set `wasSchemelessInput` as-needed for user-entered URLs. Yes, that sounds about right if we wanted to ship schemeless HTTPS-First on Android as well. But as the current plan is to ship full HTTPS-First (Bug 1921221), like was already done in Nightly, I am not sure if we should focus our efforts on bringing schemeless HTTPS-First to Android first. But on the other hand, we are currently also discussing using `wasSchemelessInput` to decide when we should **not** do a regular HTTPS-First upgrade (Bug 1919544). Considering that, I think we should actually do work on setting `wasSchemelessInput` correctly on Android. ~~I am not sure if this is something the Android team wants to work on. If not, I can also try to set up an Android environment and work on this, but that may take a bit longer than if somebody already experienced with the native android address bar code does it.~~ Ah, I just saw that Sunil already has assigned this to himself.