If I'm reading comment 1 correctly and we fast forward ~4 weeks when beta67 launches, if I am dual channel user (running nightly and beta) when beta updates I will transition from default profile on to getting a blank default-beta profile? Summarizing, I open beta66, it downloads the beta67 update, when it restarts I will get a blank default-beta profile. Wasn't this what we were actually trying to "mitigate"?
(In reply to Dave Townsend [:mossop] (he/him) from comment #1)
New versions will snatch the profile unless it has been claimed by the default browser.
In the above example, we're going to have Nightly68 and Beta67, do we understand the newer version as Nightly68 and basically Beta67 cannot snatch the "default" profile because it's a dedicated profile for Nightly68 and thus Beta67 creates the new beta-default profile?
To add more to the mix, if in the above steps we add Firefox Nightly set as default, then what happens is that Firefox Beta will get the default profile as dedicated and Nightly will create a new dedicated default-nightly. Weren't we supposed not to "snatch" the default profile from the "default browser"?
Seems to me that the current snatching behavior is quite inverted from what were expecting. Michael & Dave, could you double check the above?