Chrome Beta Adds Other Devices Menu Tab - All Your Tabs, Accessible Everywhere; Chrome's WebRTC Roadmap

The Chrome Beta channel has been updated to 19.0.1084.15 for Windows, Mac, Linux, and Chrome Frame. Well, among other, the most interesting feature with the latest Chrome Beta, lets you quickly pull up the same directions on your office computer with just one click! that you save looked up on your home computer. "When you're […]

The Chrome Beta channel has been updated to 19.0.1084.15 for Windows, Mac, Linux, and Chrome Frame. Well, among other, the most interesting feature with the latest Chrome Beta, lets you quickly pull up the same directions on your office computer with just one click! that you save looked up on your home computer.

"When you're signed in to Chrome, the tabs you have open on one device are available on all your other devices--just click the "Other devices" menu on the New Tab page. With a click, you can find and open the tab with your directions and be on your way. The tab's back and forward navigation history is also included, so you can pick up browsing right where you left off," explains Google.

Chrome Beta adds Device Menu Tab

If you use Chrome for Android Beta, the tab will also be available on your phone, right there in your pocket when you hit the road.

The Chrome team says they will be gradually rolling out the "Other devices" menu to Beta channel users over the coming week.

To give it a try, download the latest Chrome Beta and sign in to Chrome.

In other Chrome news, the Chromium team today published the roadmap of WebRTC, HTML5's new real time audio and video stack -- which was introudced to Chrome last January.

"The main parts of the WebRTC specification are now stable and are coming soon to all 200M+ Chrome users," said the team. Here is what's in?

JSEP (Javascript Session Establishment Protocol) - an API for signaling that allows for much more powerful apps and flexibility in choice of signaling protocols. "To abstract the complexity, we provide and maintain a Javascript lib that makes browser to browser calls a few lines of Javascript," explains Chromium team.

Topologies: Google says its implementation will support multiple independent PeerConnections, each capable of sending and receiving multiple independent media sources.

ICE / STUN / TURN are standardized methods for establishing a peer-to-peer connection on the Internet, even if the two end points are behind private network addresses (NAT). "We'll also support TURN servers to allow connections through tougher firewalls, where relaying and encapsulation are needed. Exactly what type of TURN will be supported is TBD," the team said.

DTLS-SRTP encryption will be mandatory for all usage of WebRTC in Chrome.

VP8, iSAC, iLBC, G.711
The video codec support by Chrome will be VP8. "On the audio side, we'll initially support iSAC, iLBC, G.711, and DTMF, with iSAC being the default," informs the chromium team.

More functionality and features will appear in future versions of Chrome including:

  • Data API. Implementation will start once the network stack is ready.
  • Screen sharing.
  • PeerConnection proxying. The ability to relay a stream to a third party will not make our first version.
  • Recording. MediaRecorder specification work has not been completed yet.