[webkit-dev] Is Bug 51742 - Add DeviceOrientationEvent.absolute blocking?
Hi, The device orientation in webkit need to add DeviceOrientationEvent.absolute to match the w3c spec: http://www.w3.org/TR/orientation-event, but I've noticed that the Bug 51742 - Add DeviceOrientationEvent.absolute has been sitting there for a long time, is it blocking? And what's the background about leaving it different from the spec? Thanks -- Best Regard, He, Xinchao ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Moving WTF out of JavaScriptCore
On Mon, Jan 9, 2012 at 8:36 PM, Eric Seidel e...@webkit.org wrote: We've been talking about moving WTF out of JavaScriptCore for a long time. We believe we're nearly there. https://bugs.webkit.org/show_bug.cgi?id=75673 This will mean that WTF will be built as a separate static library on all ports. The plan is to do this move all in one piece, after work hours PST, when the tree is least active. It won't be the most beautiful transition (as we're likely to break at least one port in the process), but we'll try not to make too much of a mess. We believe all the ports are ready for the move, except AppleWin: https://bugs.webkit.org/show_bug.cgi?id=75897 Once AppleWin is ready we'll schedule a date for the transition and announce it one this thread. Hi Eric, Is there a patch somewhere or you are still working on it? The bug link contains nothing. I would like to apply it here and test the Qt port so you'll get a bit more confidence before landing it. I believe other ports are interested too. Thanks. Thanks! -eric ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Moving WTF out of JavaScriptCore
On Tue, Jan 10, 2012 at 7:07 AM, Alexis Menard alexis.men...@openbossa.org wrote: On Mon, Jan 9, 2012 at 8:36 PM, Eric Seidel e...@webkit.org wrote: We've been talking about moving WTF out of JavaScriptCore for a long time. We believe we're nearly there. https://bugs.webkit.org/show_bug.cgi?id=75673 This will mean that WTF will be built as a separate static library on all ports. The plan is to do this move all in one piece, after work hours PST, when the tree is least active. It won't be the most beautiful transition (as we're likely to break at least one port in the process), but we'll try not to make too much of a mess. We believe all the ports are ready for the move, except AppleWin: https://bugs.webkit.org/show_bug.cgi?id=75897 Once AppleWin is ready we'll schedule a date for the transition and announce it one this thread. Hi Eric, Is there a patch somewhere or you are still working on it? The bug link contains nothing. I would like to apply it here and test the Qt port so you'll get a bit more confidence before landing it. I believe other ports are interested too. Nevermind wtf is already a static lib for Qt :D. /me is going to hide himself for not opening wtf.pro for a while. Thanks. Thanks! -eric ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] About code reviews outside bugzilla
Hi, I thought any substantial code contribution was to be reviewed in a proper bugzilla entry? This commit broke the WebKit2 build earlier today: http://trac.webkit.org/changeset/104557 No mention of a bugzilla entry... Hopefully Kenneth was quick coming up with a build fix, but please let's use Bugzilla... In the case of this patch, the build breakage would have been detected upfront by the EWS. Philippe signature.asc Description: This is a digitally signed message part ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] new API for offline web applications
Hi Dave: I have implemented abort(), but some of result of layout test in Layout/http/tests/appcache was failed. And i copy appcache dir into htdocs dir of apache raise failure again. I think due to some configuration problems. Should i configure something to correct it? thanks. huangxueqing The abort() method is defined here: http://dev.w3.org/html5/spec/Overview.html#applicationcache There is no abort() method defined in Source/WebCore/loader/appcache/DOMApplicationCache.idl. Please file a bug and attach a patch for review. See: http://www.webkit.org/coding/contributing.html Thanks! Dave On Jan 7, 2012, at 7:04 AM, huangxueqing wrote: hi all: The latest html5 specification add a API applicationCache.abort() for offline web applications. I had implement offline web app for our browser in main process this month except this interface since it need to make some modifications in WebCore. I want to know whether any guys had planed to implement it? If not and this feature was necessary, maybe i will file a bug and implement this api in next month. thanks. huangxueqing Baidu, Inc. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About code reviews outside bugzilla
The bugzilla bug is here, it's just not referenced in the message (which it should be): https://bugs.webkit.org/show_bug.cgi?id=75956 Peter On Tue, Jan 10, 2012 at 14:44, Philippe Normand ph...@igalia.com wrote: Hi, I thought any substantial code contribution was to be reviewed in a proper bugzilla entry? This commit broke the WebKit2 build earlier today: http://trac.webkit.org/changeset/104557 No mention of a bugzilla entry... Hopefully Kenneth was quick coming up with a build fix, but please let's use Bugzilla... In the case of this patch, the build breakage would have been detected upfront by the EWS. Philippe ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About code reviews outside bugzilla
On Tue, 2012-01-10 at 14:48 +, Peter Beverloo wrote: The bugzilla bug is here, it's just not referenced in the message (which it should be): https://bugs.webkit.org/show_bug.cgi?id=75956 Ah, thanks Peter! Too bad the EWS wasn't not used though :( Philippe signature.asc Description: This is a digitally signed message part ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] new shell for JavaScriptCore?
Hello JSC hackers, I've been thinking for some time now that there is room for another command-line shell for JSC. Things that the current JSC shell does not do, but it should do: * Profiling. * Disassembly. * Good debugging interfaces for developing JSC: bytecode dump, CFG dump, verbose deoptimization warnings A better shell would make it easier to develop JSC. It will make it easier to give an answer to questions like why is this code fast, but this code is slow. Specific things that one might want to support in the new shell would be meta-commands: ,profile f(1) ,disassemble f Meta-commands are commands for the shell, not expressions to be evaluated. As expressions can't begin with a comma, we would abuse the comma to introduce those meta-commands. There would also be a meta-command to inspect and modify the current heuristics, to turn the JIT on and off, etc. These options could also be turned on and off from the command line. I was hoping that `jsc' could be that new shell, but it seems that there are some strong constraints on its interface: https://bugs.webkit.org/show_bug.cgi?id=72875 So, I wanted to solicit some thoughts on this idea before going to implement it. I really think that the right place for a project like this is in WebKit proper, rather than in some external tree, as that way it will always be in sync with JSC. Thoughts? Thanks, Andy ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Moving WTF out of JavaScriptCore
On Tue, Jan 10, 2012 at 5:41 AM, Alexis Menard alexis.men...@openbossa.orgwrote: On Tue, Jan 10, 2012 at 7:07 AM, Alexis Menard alexis.men...@openbossa.org wrote: On Mon, Jan 9, 2012 at 8:36 PM, Eric Seidel e...@webkit.org wrote: We've been talking about moving WTF out of JavaScriptCore for a long time. We believe we're nearly there. https://bugs.webkit.org/show_bug.cgi?id=75673 This will mean that WTF will be built as a separate static library on all ports. The plan is to do this move all in one piece, after work hours PST, when the tree is least active. It won't be the most beautiful transition (as we're likely to break at least one port in the process), but we'll try not to make too much of a mess. We believe all the ports are ready for the move, except AppleWin: https://bugs.webkit.org/show_bug.cgi?id=75897 Once AppleWin is ready we'll schedule a date for the transition and announce it one this thread. Hi Eric, Is there a patch somewhere or you are still working on it? The bug link contains nothing. I would like to apply it here and test the Qt port so you'll get a bit more confidence before landing it. I believe other ports are interested too. Nevermind wtf is already a static lib for Qt :D. /me is going to hide himself for not opening wtf.pro for a while. To be clear, if we're talking about moving Source/JavaScriptCore/wtf = Source/WTF, there would still be project file changes necessary to support that move, so testing it wouldn't hurt :) -Jarred Thanks. Thanks! -eric ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] new API for offline web applications
How did you run the layout tests? The run-webkit-tests script should take care of starting the Apache web server for you with all the configuration options set. This is usually how you run just the http tests for a debug build (after running the build-webkit script): ./Tools/Scripts/run-webkit-tests --debug http Do the same tests pass without your changes? That would be the first thing to check. You should also write at least one layout test that tests the new abort() method. See Step 4 here: http://www.webkit.org/coding/contributing.html Dave On Jan 10, 2012, at 6:46 AM, huangxueqing wrote: Hi Dave: I have implemented abort(), but some of result of layout test in Layout/http/tests/appcache was failed. And i copy appcache dir into htdocs dir of apache raise failure again. I think due to some configuration problems. Should i configure something to correct it? thanks. huangxueqing The abort() method is defined here: http://dev.w3.org/html5/spec/Overview.html#applicationcache There is no abort() method defined in Source/WebCore/loader/appcache/DOMApplicationCache.idl. Please file a bug and attach a patch for review. See: http://www.webkit.org/coding/contributing.html Thanks! Dave On Jan 7, 2012, at 7:04 AM, huangxueqing wrote: hi all: The latest html5 specification add a API applicationCache.abort() for offline web applications. I had implement offline web app for our browser in main process this month except this interface since it need to make some modifications in WebCore. I want to know whether any guys had planed to implement it? If not and this feature was necessary, maybe i will file a bug and implement this api in next month. thanks. huangxueqing Baidu, Inc. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] generate-coverage-data on Lion?
Hi All, When attempting to run code coverage on Lion I am getting the error below. Has anyone successfully gotten generate-coverage–data to work on Lion or have insight into the error? Could this be a llvm/clang version issue? Any tips would be greatly appreciated. Thanks, -Larry … /WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/JavaScriptCore ld: library not found for -lgcov Command /Developer/usr/bin/clang++ failed with exit code 1 ** BUILD FAILED ** The following build commands failed: Ld /Users/xyz/WebKit/WebKitBuild/Debug/JavaScriptCore.framework/Versions/A/JavaScriptCore normal x86_64 (1 failure) Died at /Users/xyz/WebKit/Tools/Scripts/generate-coverage-data line 62. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Moving WTF out of JavaScriptCore
If a Qt person wants to make this move even less error-prone for Qt, adding a newwtf.a library which just builds WTF/Stub.cpp and links it into JavaScriptCore (similar to what Mac, Gtk, and Chromium do today), then there won't need to be any guess work on my part when moving wtf.a I'll have newwtf.a as an example. If you look in Source/WTF/ you can see examples of how Gtk, Mac and Chromium build/link in newwtf.a today. On Tue, Jan 10, 2012 at 7:41 AM, Jarred Nicholls jar...@webkit.org wrote: On Tue, Jan 10, 2012 at 5:41 AM, Alexis Menard alexis.men...@openbossa.org wrote: On Tue, Jan 10, 2012 at 7:07 AM, Alexis Menard alexis.men...@openbossa.org wrote: On Mon, Jan 9, 2012 at 8:36 PM, Eric Seidel e...@webkit.org wrote: We've been talking about moving WTF out of JavaScriptCore for a long time. We believe we're nearly there. https://bugs.webkit.org/show_bug.cgi?id=75673 This will mean that WTF will be built as a separate static library on all ports. The plan is to do this move all in one piece, after work hours PST, when the tree is least active. It won't be the most beautiful transition (as we're likely to break at least one port in the process), but we'll try not to make too much of a mess. We believe all the ports are ready for the move, except AppleWin: https://bugs.webkit.org/show_bug.cgi?id=75897 Once AppleWin is ready we'll schedule a date for the transition and announce it one this thread. Hi Eric, Is there a patch somewhere or you are still working on it? The bug link contains nothing. I would like to apply it here and test the Qt port so you'll get a bit more confidence before landing it. I believe other ports are interested too. Nevermind wtf is already a static lib for Qt :D. /me is going to hide himself for not opening wtf.pro for a while. To be clear, if we're talking about moving Source/JavaScriptCore/wtf = Source/WTF, there would still be project file changes necessary to support that move, so testing it wouldn't hurt :) -Jarred Thanks. Thanks! -eric ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] [PATCH] Use 'Ok' and 'Cancel' buttons in JavaScript confirm box.
See: http://www.javascripter.net/faq/confirm.htm
Fixes: https://bugs.kde.org/show_bug.cgi?id=287629
---
Source/WebKit/qt/Api/qwebpage.cpp |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Source/WebKit/qt/Api/qwebpage.cpp
b/Source/WebKit/qt/Api/qwebpage.cpp
index 8f0f153..acd2bd6 100644
--- a/Source/WebKit/qt/Api/qwebpage.cpp
+++ b/Source/WebKit/qt/Api/qwebpage.cpp
@@ -2119,7 +2119,7 @@ void QWebPage::javaScriptAlert(QWebFrame *frame, const
QString msg)
This function is called whenever a JavaScript program running inside \a
frame calls the confirm() function
with the message, \a msg. Returns true if the user confirms the message;
otherwise returns false.
-The default implementation executes the query using
QMessageBox::information with QMessageBox::Yes and QMessageBox::No buttons.
+The default implementation executes the query using
QMessageBox::information with QMessageBox::Ok and QMessageBox::Cancel buttons.
*/
bool QWebPage::javaScriptConfirm(QWebFrame *frame, const QString msg)
{
@@ -2128,7 +2128,7 @@ bool QWebPage::javaScriptConfirm(QWebFrame *frame, const
QString msg)
return true;
#else
QWidget* parent = (d-client) ? d-client-ownerWidget() : 0;
-return QMessageBox::Yes == QMessageBox::information(parent, tr(JavaScript
Confirm - %1).arg(mainFrame()-url().host()), Qt::escape(msg),
QMessageBox::Yes, QMessageBox::No);
+return QMessageBox::Ok == QMessageBox::information(parent, tr(JavaScript
Confirm - %1).arg(mainFrame()-url().host()), Qt::escape(msg),
QMessageBox::Ok, QMessageBox::Cancel);
#endif
}
--
1.7.7
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] [PATCH] Use 'Ok' and 'Cancel' buttons in JavaScript confirm box.
Thanks, but we don't usually accept patches via the mailing list.
Instead, we use https://bugs.webkit.org/.
Please see http://www.webkit.org/coding/contributing.html for more
information about how to contribute patches to the project.
Adam
On Tue, Jan 10, 2012 at 11:29 AM, Johannes Obermayr
johannesoberm...@gmx.de wrote:
See: http://www.javascripter.net/faq/confirm.htm
Fixes: https://bugs.kde.org/show_bug.cgi?id=287629
---
Source/WebKit/qt/Api/qwebpage.cpp | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Source/WebKit/qt/Api/qwebpage.cpp
b/Source/WebKit/qt/Api/qwebpage.cpp
index 8f0f153..acd2bd6 100644
--- a/Source/WebKit/qt/Api/qwebpage.cpp
+++ b/Source/WebKit/qt/Api/qwebpage.cpp
@@ -2119,7 +2119,7 @@ void QWebPage::javaScriptAlert(QWebFrame *frame, const
QString msg)
This function is called whenever a JavaScript program running inside \a
frame calls the confirm() function
with the message, \a msg. Returns true if the user confirms the message;
otherwise returns false.
- The default implementation executes the query using
QMessageBox::information with QMessageBox::Yes and QMessageBox::No buttons.
+ The default implementation executes the query using
QMessageBox::information with QMessageBox::Ok and QMessageBox::Cancel buttons.
*/
bool QWebPage::javaScriptConfirm(QWebFrame *frame, const QString msg)
{
@@ -2128,7 +2128,7 @@ bool QWebPage::javaScriptConfirm(QWebFrame *frame,
const QString msg)
return true;
#else
QWidget* parent = (d-client) ? d-client-ownerWidget() : 0;
- return QMessageBox::Yes == QMessageBox::information(parent,
tr(JavaScript Confirm - %1).arg(mainFrame()-url().host()),
Qt::escape(msg), QMessageBox::Yes, QMessageBox::No);
+ return QMessageBox::Ok == QMessageBox::information(parent,
tr(JavaScript Confirm - %1).arg(mainFrame()-url().host()),
Qt::escape(msg), QMessageBox::Ok, QMessageBox::Cancel);
#endif
}
--
1.7.7
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] new shell for JavaScriptCore?
On Jan 10, 2012, at 7:33 AM, Andy Wingo wrote: Hello JSC hackers, I've been thinking for some time now that there is room for another command-line shell for JSC. Hi Andy, Yes! Some more things to add to the wish list: * tab completion (e.g. Math.si -tab- Math.sin) * persistant command history over invocations * binding results of prior commands to variables in global scope. (I believe that the readline library has some useful hooks we're not currently using to help with the first two of these). Specific things that one might want to support in the new shell would be meta-commands: ,profile f(1) ,disassemble f Meta-commands are commands for the shell, not expressions to be evaluated. As expressions can't begin with a comma, we would abuse the comma to introduce those meta-commands. I'd suggest that it might be better to expose new commands through JavaScript where possible, rather than using a new syntax. One key advantage is that if these commands are exposed through JavaScript then you can easily script use of the shell commands in JS, e.g. to disassemble all the functions on object foo's prototype: for (var func in foo.prototype) disassemble(foo.prototype[func]); There would also be a meta-command to inspect and modify the current heuristics, to turn the JIT on and off, etc. These options could also be turned on and off from the command line. It would be a really great if any new shell were not just be limited to being useful to WebKit developers, but was also suitable for use by programmers wanting to script in JavaScript. Some of the tools you have listed should be extremely useful to us in developing JSC, but would probably be inappropriate to ship to customers, so we might want the option to be able to compile these out in some builds. But I don't think that this should be a constraint in any way – we might just want to wrap some of the tools in #ifdefs, or maybe guard them on an environment variable being set. So, I wanted to solicit some thoughts on this idea before going to implement it. I really think that the right place for a project like this is in WebKit proper, rather than in some external tree, as that way it will always be in sync with JSC. Yes! - we'd definitely love to have a better shell in the project. One other random thought, it might be desirable if the shell were written to the JSC API, rather than being written directly against JSC's internal headers. If the current API is insufficient we can expose some additional functionality through private headers. This is certainly not a requirement, but it would be a cleaner way to do things, and would serve as a really great test for the utility design of our API (and may be helpful in informing future improvements). cheers, G. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] ietestcenter tests
Hi webkit-dev, As you're probably aware, our friend at Microsoft have posted a bunch of standards compliance tests on http://samples.msdn.microsoft.com/ietestcenter/. In the spirit of good-natured competition, I thought we might try to get a higher score than the latest beta of IE10. (WebKit's score is already higher than IE9, so there's not much of a challenge there.) I've compiled a spreadsheet of the tests we're failing: https://docs.google.com/spreadsheet/ccc?key=0AppchfQ5mBrEdHAtbzNvcFdfSlBBbGN0NjY1UFlLYlE Many of these bugs look to be pretty easy to fix, so if you're just starting out in WebKit or looking to learn about a new area of the project, these might be good places to start. Seasoned contributors are also welcome, of course. :) Happy hacking, Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] ietestcenter tests
On Tue, Jan 10, 2012 at 5:22 PM, Adam Barth aba...@webkit.org wrote: Hi webkit-dev, As you're probably aware, our friend at Microsoft have posted a bunch of standards compliance tests on http://samples.msdn.microsoft.com/ietestcenter/. In the spirit of good-natured competition, I thought we might try to get a higher score than the latest beta of IE10. (WebKit's score is already higher than IE9, so there's not much of a challenge there.) I've compiled a spreadsheet of the tests we're failing: https://docs.google.com/spreadsheet/ccc?key=0AppchfQ5mBrEdHAtbzNvcFdfSlBBbGN0NjY1UFlLYlE Many of these bugs look to be pretty easy to fix, so if you're just starting out in WebKit or looking to learn about a new area of the project, these might be good places to start. Seasoned contributors are also welcome, of course. :) Happy hacking, Adam Good deal, thanks for sharing Adam. Jarred ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] SWF File with flv/f4v streaming from server doesn't play with the webkit application.
Hi, I have developed an application using webkit which plays back youtube videos, SWF files and flv/f4v files. For playing back flv/f4v files I have a swf file created using actionscript. This swf file looks for an xml file at a predefined path. This xml file contains path to a flv/f4v file. The swf file plays back this flv/f4v file in my application using adobe flash player plugin. When I give any local flv/f4v file in the xml file, the SWF file plays fine. But if I give a streaming url [http://pseudo01.hddn.com/vod/demo.flowplayervod/Extremists.flv] SWF file doesn't get played. I cross verified in firefox and chrome, I am getting the same result as my application is responding. When I take the same swf file to a Windows7 machine [64 Bit], it works fine in Adobe Flash Player 11.1. Can anyone tell me why am I not able to play flv/f4v streaming url files. I am using: OS: FC15, 64 Bit Kernel: 3.0 Webkit:1.4.0 chrome: latest firefox: 4.x Flash Player: 11.0.1.152 Regards, Avinash. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
