The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Hi Mike.
Here's an e-mail (of Jan 2015) from webkit-dev:
https://lists.webkit.org/pipermail/webkit-dev/2015-January/027196.html
from which I can see the work on WebRTC support in WebKit is (was on that date) still in progress. The version of WebKit we've last updated to is of Feb 2014, a year older.
Also, currently we don't even compile the sources related to webrtc. The JavaFX media component (used in WebView to play media content) is based on GStreamer which may be a base for webrtc, however we haven't yet investigated it. (Will it work from scratch, being supported by WebKit, or will we have to add some new glue code b/w WebKit and FX media?).
Please, file a JIRA issue (enhancement).
22-04-2015
Maybe this ... http://www.openwebrtc.io is not the same Webrtc thats inside jdk9
Is it?
16-04-2015
Does this Webkit support Webrtc on Desktop? How do I find out exactly what is being put inside?
Filed RT-40105 to track the needed compiler upgrade changes. RT-36726 (this JIRA) and RT-40105 are interdependent, but will be pushed as separate changesets for tracking purposes.
20-02-2015
Almost all of the work is complete and will be integrated into JDK 9 soon. There is a fairly small amount of work to backport to 8u60, but it will use the exact same code base.
13-02-2015
This is tracked by the following JEP: https://bugs.openjdk.java.net/browse/JDK-8044852
13-02-2015
Is this ticket still on track? To which webkit version will JavaFX 8u40 be updated? Does this fix the scrolling performance issues (RT-33217)?
01-09-2014
- We need to understand what to do with the fact, that webview is now built by VS 2013 Express on Win, and by clang (shipped with Xcode 4.6) on Mac. (on Linux?)
- Further process looks as follows to me:
1) reanimate JS
2) start to implement critical missing functionality, revise all the other todo's in the code
3) test manually the whole functionality (we need some test draft, probably), collect issues, fix critical ones
4) update the DRT tests (not yet), run it, rate the failures, fix critical ones
5) clean up the build scripts
6) build, run and test on Linux
08-05-2014
Shortly, current state of the merge: I've managed to build and run the merged webview on Mac & Win platforms. JavaScript crashes on Mac and doesn't work on Win (but doesn't crashes). Stuff like images, text & mouse input, navigation across the links, scrolling etc. work pretty well from the first glance, however episodic crashes happen. There's lots of todo things, in general.
08-05-2014
The attached webkit-merge-journal.txt file is a free-form, raw document where I tried to journalize the process of the merge - steps, problems, solutions, workarounds, todo's etc.