In 22.0 Mozilla also announced official support for teleconferencing through WebRTC. We should, at least in theory, be able to support this given a fast enough Mac. It may well be hopeless for almost all G3s, but I should think voice-only comms should work for most G4s, and the high end G5s might even be able to do video. I don't really want to announce WebRTC support until it's been tested, though, and my unusual network setup may be interfering with testing. I'd like to see how others do with the WebRTC demo -- go to the apprtc. link at the top and it will provide a connect URL for another user to connect to. Oddly, on my network, it simply connected to itself, but I have a rather unfriendly firewall and I suspect it is interfering with the peer-to-peer communication protocol. That said, my antisocial chat with myself in full video and audio proceeded at nearly full speed on this quad. Please post your testing results in the comments. If it appears to work well, then it will be officially supported in whatever the next stable branch happens to be.
I'm removing all the methodjit stuff from the changesets, and then it will be BaselineCompiler or bust after that. Do not expect a 24 aurora any time soon. If there are high or critical severity security issues repaired in 23, I will issue a 22.0.1 interim release with those issues if 24 is not ready for testing. Remember, 24's JavaScript performance will be worse. The idea is to hopefully get away with it.
At apprtc.appspot.com after allowing video and audio from my iSight, I got "Connecting…", then "Waiting for someone to join: ……" I see my own video (rather fluently), but don't hear any audio. My firewall is completely disabled right now. Waited for 10 minutes, but nobody joined. This was at 11:45 UTC (07:45 EST), will try again later.
ReplyDeleteAt apprtc.appspot.com after allowing video and audio from my iSight, I got "Connecting…", then "Waiting for someone to join: ……" I see my own video (rather fluently), but don't hear any audio. My firewall is completely disabled right now. Waited for 10 minutes, but nobody joined. This was at 11:45 UTC (07:45 EST), will try again later.
ReplyDeleteYou might have to hand the link to someone and say "connect at such and such a time." I tried doing this with a Chromebook and the G5, but the G5 is behind the firewall. I didn't get audio until it "connected," but presumably from the feedback it clicked and echoed, so I admit I didn't test that thoroughly. Video was very good, though.
DeleteOh, I see. I'll be at https://apprtc.appspot.com/?r=98680094 for the next hour, then, if someone wants to test this.
DeleteNobody joined at my one hour try. I then tried to make a call between my G4 PB and my G3 iBook. Doesn't seem to work too well.
DeleteLetting the PB G4 connect with video and audio, I managed to get the iBook (audio only) to establish a connection (presumably, since the page displayed "Hang up" at the bottom), however as soon as the iBook was connected, the G4 PB was thrown out of the room and fell back to "Connecting".
Sticking the iSight onto the iBook gave me the opposite result. Now it was thrown out of the room as soon as the PB G4 connected with audio-only capabilities. I never had any video or audio coming through on either side.
Using audio only on both sides, both display "Connecting…" and stay at that. Trying to reload the page gave me "Sorry, this room is full. Click here to try again." (useless).
Maybe the apprtc site is overloaded right now, or audio only on one side or both sides isn't possible. I don't have a second webcam. And the iBook is connected to the internet via AirPort routed through the PB G4, so maybe that's the issue.
BTW, notice the Lion style scroll bars in responsive design view (cmd+opt+M)? Hm…
ReplyDeleteIt looks like both the NoScript menu and Remember Password popup problems are gone. Thanks!
ReplyDeleteUnwanted search engines are still added with every new version though. I guess I'll just have to delete them every time.
Glad to hear it, though it wasn't anything specific I did -- I imagine it got fixed by Mozilla with other things.
Delete