Forum Discussion
MicrosoftDev channel update to 93.0.916.1 is live
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
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.rshupak Looks like that was indeed an unintentional change! The fix should be in Dev this week or next week. Thanks for finding this!
josh_bodner Great news!
Any chance that the sorting of other host names can be fixed too. As I noted before, the allow/block/clear lists for cookies on edge://settings/content/cookies, the don't clear list on edge://settings/clearBrowsingDataOnClose, as well as edge://settings/privacy/trackingPreventionExceptions. These all use sort by reversing all components, for example
This should be
- aaa.aaa.com
- bbb.aaa.com
- aaa.aaa.org
- aaa.bbb.com
- bbb.bbb.com
- bbb.bbb.org
Rich
- josh_bodner
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.
- While 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_bodnerDifferent team, but I'll let them know too!
