![]() ![]() Any Firefox that still only accepts the old format is waaaaaaaay out of date by now. Additionally, when support for the old format went away (in 72), all supported versions of Firefox supported the new format. Firefox gained support for the new format back in 68, and parsed both until version 72. Then after a few versions pull parsing of the old format. ![]() ![]() So in newer versions of FF support parsing both the old and new formats, but log a deprecation notice in the console when old one is used. What might help, going forward, is to have overlaps between supported formats, and logging deprecation warnings. I think this too complex of a feature-detection strategy for API users to do, and also very error-prone. You could have two simple SDPs that are identical except for the simulcast format if the new one works, then use the new format. I'd also imagine that because of that at some point Firefox would probably stop leaking version number there. But that really does get around the user's intention of trying to hide their Firefox version from us. (In reply to Saeed Jahed from comment #38) That could be used to reliably detect old Firefox.Īt this point, I'm considering just using the new format regardless of Firefox version, as the usage of older versions of Firefox that required older SDP is probably very low. If all else fails, you could inspect our o= line, which has had the version in it for a really long time. It might also be because you're using Firefox that doesn't support simulcast at all, which means using the new format won't be any worse than using the old. If the old one fails too, that probably means you're on a newer Firefox either sRD is just broken for some crazy reason, and this is likely newer Firefox because that's the baseline, or you have a newer Firefox that is implementing some new validity checking that your SDP is failing, so you should use the new format. But there are other reasons where applying SDPs might throw an error and so it's probably not great to feature-detect that way. We can feature detect by using the old format and seeing if it throws an error. While, the new one (I think post Firefox 68), only allowed: What is Firefox's recommended way of feature-detecting this change? The old SDP parser allowed: (In reply to Saeed Jahed from comment #36) Saeed, Firefox supports the new syntax on all supported versions, are you seeing a lot of usage on versions lower than 68? Maybe it would be best if Meet switched to the new syntax for all Firefox? I'll revert to canvas fingerprinting blocking via an add-on for now. The flag also seems to disable overriding the userAgent via add-ons or the setting. Toggling this flag allows access to Meet. privacy.resistFingerprinting was true, which reports the FF version as the ESR version (68.0). Ask me anything.ĭoes this happen with a fresh profile? You have upgraded to 72, but for some reason Meet thinks you're still running an old version of Firefox, and is using an obsolete syntax as a result.įound it. I have a similar configuration to Alex, but the problem persists with all plugins turned off. No progress for a month, and this is still broken in 72.0.2 for me. (In reply to Byron Campen (PTO until Feb 5) from comment #24) How can I troubleshoot this further without clobbering everything in the session? The moment I updated to 72.0, however, Meet was broken. I have a million (fine, actually several hundred) tabs open across perhaps 20 windows, and every time I've updated Firefox there has been no problem the saved session state was resumed flawlessly and everything Just Worked. I then cloned the files making up my profile into a new profile and launched a separate copy of Firefox with that profile (via button to do so in about:profiles), and the problem still persisted.įinally I force-quit the cloned Firefox, removed the saved session state from the cloned profile, and relaunched it. I then tested many times after actually removing all my plugins, one by one, reloading the Meet page after each plugin was removed. I then tested with all plugins disabled, and it still seemed broken. I originally tested with all my plugins enabled, and it seemed broken. This might be something wrong with Firefox, but not what I'm reporting. ![]()
0 Comments
Leave a Reply. |