> Yes, I haven't tested my patch in that situation. Will do. I didn't test with 2 PCs but by running two instances of TB 116 (with my patch and configured and ignore subscriptions in "advanced" imap settings) both with the same deeply nested account. I'm able to create deeply nested folder and see them on the other instance with new folders set to subscribed or un-subscribed. Also, FWIW, after folders are fully expanded one time after initial account creation in the TB instance, the folder collapse/expand can be done on the immediate folder, not the one above. So the issue shown in comment 40 probably only applies right after initial account creation. So you probably won't see this if you just run 115 with my patch from an existing profile/account. I can make a "try" build on release 115.0 with my proposed patch applied if you would like to test it for yourself. Let me know.
Bug 1843637 Comment 46 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Yes, I haven't tested my patch in that situation. Will do. I didn't test with 2 PCs but by running two instances of TB 116 (with my patch and configured withignore subscriptions in "advanced" imap settings) both with the same deeply nested account. I'm able to create deeply nested folder and see them on the other instance with new folders set to subscribed or un-subscribed. Also, FWIW, after folders are fully expanded one time after initial account creation in the TB instance, the folder collapse/expand can be done on the immediate folder, not the one above. So the issue shown in comment 40 probably only applies right after initial account creation. So you probably won't see this if you just run 115 with my patch from an existing profile/account. I can make a "try" build on release 115.0 with my proposed patch applied if you would like to test it for yourself. Let me know.
> Yes, I haven't tested my patch in that situation. Will do. I didn't test with 2 PCs but by running two instances of TB 116 (with my patch and configured with ignore subscriptions in "advanced" imap settings) both with the same deeply nested account. I'm able to create deeply nested folder and see them on the other instance with new folders set to subscribed or un-subscribed. Also, FWIW, after folders are fully expanded one time after initial account creation in the TB instance, the folder collapse/expand can be done on the immediate folder, not the one above. So the issue shown in comment 40 probably only applies right after initial account creation. So you probably won't see this if you just run 115 with my patch from an existing profile/account. I can make a "try" build on release 115.0 with my proposed patch applied if you would like to test it for yourself. Let me know.