January 15 Deployment - Expected Behavior re Favorites

"What folders are the duplicates in? (There may be up to one copy of each favorite in the ~3 folders, but there shouldn't be duplicates in the same folder.)"

As reported in the thread "Deployment - Fonts, Favorites, Sync", duplicates occurred on the Favorites Bar and duplicates were created in "Other Favorites", although the duplication in "Other Favorites" occurred as a result of creation of a subfolder labeled "Bookmarks Menu".

BEGIN EXCERPTS

Here are relevant excerpts from the report in the thread "Deployment - Fonts, Favorites, Sync":

As discussed in other threads, I prepared to test EdgeChromium installation by creating two identical lists of Favorites/Bookmarks, one in EdgeClassic and one in EdgeChromium. To "fingerprint" the source, I marked all Favorites/Bookmarks in EdgeClassic with an "E" or an "e" and marked all Favorites/Bookmarks in EdgeChromium with a "C" or a "c".''

That created these sets of Favorites/Bookmarks:

(1) EDGE CHROMIUM BEFORE INSTALLING MicrosoftEdgeEnterpriseX64.msi:

On the Favorites Bar:
ForumC,MmailC,YmailC,GmailC,FBc,BingC,GmpsC,AmzC,RtrC,NflxC,ABc,JMGc,TWCc,tURLc,MSNc,511C
In "Other Favorites":
NEWSc-Advocate,NEWSc-Alternet, NEWSc-Capitol Times, NEWSc-Politics Today-Early & Often, NEWSc-Mother Jones, NEWSc-New York Times, NEWSc-Politico, NEWSc-Real Clear Politics, NEWSc-Washington Post, NEWSc-Wisconsin State Journal, NEWSc-Wonkette, MARKER1**, MARKER2**

(2) EDGE CLASSIC BEFORE INSTALLING MicrosoftEdgeEnterpriseX64.msi:

On the Favorites Bar:
ForumE,MmailE,YmailE,GmailE,FBc,BingE,GmpsE,AmzE,RtrE,NflxE,ABe,JMGc,TWCe,tURLe,MSNe,511E
In "Bookmarks Menu":
NEWSe-Advocate,NEWSe-Alternet, NEWSe-Capitol Times, NEWSe-Politics Today Early & Often, NEWSe-Mother Jones, NEWSe-New York Times, NEWSe-Politico, NEWSe-Real Clear Politics, NEWSe-Washington Post, NEWSe-Wisconsin State Journal, NEWSe-Wonkette, MARKER1**, MARKER2**

I then ran the MicrosoftEdgeEnterpriseX64.msi installation routine, resulting in this set of Favorites/Bookmarks:

(3) EDGE CHROMIUM AFTER INSTALLING MicrosoftEdgeEnterpriseX64.msi:

On the Favorites Bar:
ForumC,MmailC,YmailC,GmailC,FBc,BingC,GmpsC,AmzC,RtrC,NflxC,ABc,JMGc,TWCc,tURLc,MSNc,511C,ForumE,MmailE,YmailE,GmailE,FBc,BingE,GmpsE,AmzE,RtrE,NflxE,ABe,JMGc,TWCe,tURLe,MSNe,511E
In "Other Favorites":
NEWSc-Advocate,NEWSc-Alternet, NEWSc-Capitol Times, NEWSc-Politics Today-Early & Often, NEWSc-Mother Jones, NEWSc-New York Times, NEWSc-Politico, NEWSc-Real Clear Politics, NEWSc-Washington Post, NEWSc-Wisconsin State Journal, NEWSc-Wonkette, MARKER1**, MARKER2**
In an "Other Favorites" subfolder titled "Bookmarks Menu":
NEWSe-Advocate,NEWSe-Alternet, NEWSe-Capitol Times, NEWSe-Politics Today Early & Often, NEWSe-Mother Jones, NEWSe-New York Times, NEWSe-Politico, NEWSe-Real Clear Politics, NEWSe-Washington Post, NEWSe-Wisconsin State Journal, NEWSe-Wonkette, MARKER1**, MARKER2**

END EXCERPTS

"And have you seen this behavior in Canary or Dev?"

No, but I have not been able to test the behavior in either Canary or Dev because neither build (as far as I know) removes LegacyEdge and brings over Favorites/Bookmarks to NewEdge upon installation.  Obviously, whatever duplicates are created upon installation of Stable will sync to Canary and Dev builds.

I have also not tested whether or not the duplication behavior occurs upon Stable installation.  Prior to installing Stable on my production computers, I removed each and every Favorite from LegacyEdge so that no Favorites at all would be imported from LegacyEdge.  I intend to follow a similar procedure when I do the railroad's computers -- backup LegacyEdge Favorites to an HTML file, remove each and every Favorite from LegacyEdge, install Stable, then import from the HTML file.  I haven't tested that procedure, but I'm certain that it will work okay, so long as no instance of LegacyEdge has any Favorites to import.

===================
** MARKER1 and MARKER2 were favorites/bookmarks created to test whether the cutover process would treat absolutely identical favorites/bookmarks as duplicates, eliminating one set on cutover. MARKER1 points to an identical link in both the EdgeClassic and EdgeChromium sets, as does MARKER2. The cutover process did not identify either MARKER1 or MARKER2 as duplicates of one another and eliminate one or the other when cutting over.