And I already replied that I won't "debug" the viewer, because there was no bug in it in the first place !
This device is buggy/badly designed. Forget it, or report the issue to its maker.
It is the normal and expected behaviour
that faces bearing a media get all their left-click actions passed to the media plugin, and not to the object (and its script) itself
And yes, it is also normal that right clicks, being used for the pie menu, are not passed, and that the "Touch" action in that pie menu keeps transmitting the touch to the right-clicked *object* (here, it's not a click on a media, but a touch on an object).
Keep in mind that the Cool VL Viewer is not using the same UI as v2+ viewers and those viewers which adopted v2's UI code (SIngularity, for instance): my viewer kept, on purpose, the same UI code (debugged, expanded and improved, but still with the same working logic) as the v1 viewer it was forked from. I do not intend to change this part of the viewer code (which is deeply intricated with its inner working). The touch routines are also different (there are two kind of "touches" for in-world objects, one "sync" and one "async", the latter requiring data to be sent by the server whenever that data about the touched object is not already present and cached in the viewer memory). The Cool VL Viewer uses async touches a lot, while v2 viewers use sync touch (relying on possibly outdated information).
My understanding of the "problem", here, is that the other viewers cache the "non-media" state of the object when it is rezzed (normal: media data is sent later) and therefore still pass touches to its scripts instead of passing it to the media plugin. The Cool VL Viewer, on the contrary, passes the click to the plugin as soon as the media data is received (thanks to the async touch)...
That object should not be using its screen to detect touch that must interact with the scripts: it should bear buttons around the screen for this purpose. Touch to the screen are touch directed to the played media. Period.
Do you know what info and warning messages I added to the viewer code and where ? Do you know their purpose ? No, you don't. So, don't assume and comply with the rules. Any new bug report without attached logs from you will from now on be ignored, for my time is limited and I won't repeat myself yet again
Case closed. Not a bug, but expected behaviour.