Whatever the solution is, I hope this can be resolved as soon as possible. Please note that this issue affects website functionality on a lot of websites, like embedded maps, videos, and more that can no longer be loaded at all in private mode or even in regular mode with strict tracking protection. It may not be a regression from the Firefox POV, but from the user's POV it's a regression, as it's a recent and undocumented change in behavior. Normally, website developers implement an opt-in that users see instead of the embedded thing so that they can give the consent by demand, but that's broken as well due to this issue. There is no indication to the user that it's caused by the tracking protection (apart from a console warning, where the regular user usually can't see a relation to the problem), and it just makes no sense that a CDM is blocked by the tracking protection. This is not only an issue for users of the affected websites. I integrated CookieBot for several hotel websites in the last few months, and for hotel websites it can have a real impact on their revenue if potential guests can't see the location on a map, or the embedded videos that presents the destination because these things can influence the decision to book or not to book.
Bug 1899092 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Whatever the solution is, I hope this can be resolved as soon as possible. Please note that this issue affects website functionality on a lot of websites, like embedded maps, videos, and more that can no longer be loaded at all in private mode or even in regular mode with strict tracking protection. It may not be a regression from the Firefox POV, but from the user's POV it's a regression, as it's a recent and undocumented change in behavior. Normally, website developers implement an opt-in that users see instead of the embedded thing so that they can give the consent by demand, but that's broken as well due to this issue. There is no indication to the user that it's caused by the tracking protection (apart from a console warning, where the regular user usually can't see a relation to the problem), and it just makes no sense that a CMP is blocked by the tracking protection. This is not only an issue for users of the affected websites. I integrated CookieBot for several hotel websites in the last few months, and for hotel websites it can have a real impact on their revenue if potential guests can't see the location on a map, or the embedded videos that presents the destination because these things can influence the decision to book or not to book.