Bug 29587
Summary: | [Qt] webview doesn't respond to click on youtube video | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tor Arne Vestbø <vestbo> |
Component: | Plug-ins | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | jturcotte, kenneth, tonikitoo |
Priority: | P2 | Keywords: | Qt |
Version: | 528+ (Nightly build) | ||
Hardware: | Other | ||
OS: | Windows XP |
Tor Arne Vestbø
This bug report originated from Nokia internal issue QT-1864
--- Comments ---
Function: webkit
Version: 4.5.2
Platform: WindowsXP
macbook, windows xp, visual studio 2008 express
Compiler: MSVC
nothing
Short description: webview doesn't respond to click on youtube video
Did:
i'm not sure if this is a bug. i want to implement a feature with the qt webkit, such that when i click on a webpage element, such as an image, the browser can detect what I've just clicked. for example, if i click on an image, the browser can tell me that i just clicked on an image. i tried to implement this with the hitTestContent function. i added the hit test inside a webview mousePressEvent function, the code i'm modifying is the browser demo of the QT4.5.2. everything works fine until i tried to click on youtube videos or hulu videos. the mousePressEvent is not called at all when i click on the video, however the function does work for some other flash video site. i don't why. i think this might be a bug. eventually i want my program to detect the flash video under the mouse click, but now i'm stuck.
Expected to see:
just set a break point in the mousePressEvent function under webview.cpp of the Qt4.5.2 browser demo. and run the demo and browse a youtube video page and click on the video and then click on somewhere else. the mousePressEvent should respond to both clicking.
Got instead:
the mousePressEvent doesn't respond to clicking on the youtube video.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Jocelyn Turcotte
NPAPI plugins windows are most of the time associated to a different event loop.
My guess is that this is not a supported behavior.
Closing as invalid, please re-open if a different point of view is felt.