Forum Discussion
josh_bodner
Jun 15, 2021Microsoft
Dev channel update to 93.0.916.1 is live
Hello Insiders! Today we’re releasing build 93.0.916.1 to the Dev channel. Alongside this, we’re excited to announce a campaign to spur extension development and usage: https://techcommunity.micro...
rshupak
Jun 15, 2021Iron Contributor
josh_bodner I only just noticed this the other day in canary but apparently it is broken in beta, dev, and canary while still correct in stable. Specifically, the sorting of site names in the password list changed from an intelligent sort by eTLD+1 then the prefix to sorting by the entire host name. The consequence of this is that with the good sort, related hosts are grouped together as shown below.
With the new bad sort order, related hosts are scattered around.
To be blunt, wherever host names are sorted, they should be sorted by eTLD+1 then prefix so that related sites are grouped.
josh_bodner
Jun 17, 2021Microsoft
rshupak since we used to have those sorted correctly, I can't imagine that this change was intentional, so I'll ask the team about it.
- rshupakJun 17, 2021Iron ContributorWhile at it, please have them fix the sorting of the cookie block, allow, and clear on exit lists onedge://settings/content/cookies. These inappropriately sort by reverse order the host name components so that all .co hosts sort before all .com before all .net before all .org. This is really weird. This too should use eTLD+1 with the modification that an entry in the list may be an eTLD which is sorted as is.
All site name lists should likely be sorted as eTLD+1 then prefix for the same reason.- josh_bodnerJun 24, 2021MicrosoftDifferent team, but I'll let them know too!
- rshupakJun 26, 2021Iron ContributorSorting of edge://settings/passwords was fixed today or yesterday. Thanks. The other lists still sort poorly.