On Thu, Jun 18, 2015 at 09:27:51AM -0400, Tim Moody wrote: > > summary: you have a failing video _player_ app, not a failing > > _video_. > > OK. I thought maybe it was a variant mp4, but I see that you are > right. It is the browser support for the page not the codec. > > To be clear, I am using browse in both the case where the video > plays and the case where it doesn't. But your point about the html > and javascript that wrap the video that doesn't play is a good one. > I had already tried looking at the source, but nothing jumps out. > Thanks for the alternative ways of trying the page on the xo4. > > But if this is the answer then I'm pretty much stuck unless browse > can be modified to handle what other browsers can handle.
You're stuck if developers can't reproduce the problem. You can help the developers; differential diagnosis procedure relies on tests of the software components. Browse is a wrapper around WebKit. On the XO-4 you can find a WebKit browser that isn't Browse. /usr/libexec/webkitgtk3/GtkLauncher If the problem occurs with that, then it is not a problem with Browse at all, and you would need to speak with the WebKit people. And their first response might be to upgrade, which brings us back to the rainbow pooing unicorn problem in devel@ and support-gang@ > The page in question starts at TED, is wrapped in a zim file by > kiwix, and rendered by the kiwix server. Mostly meaningless. You're presuming too much knowledge on my part. > My plan is to put a server on the open internet that has this page, > but I haven't gotten to it yet. I'll let you know if you're > interested. You're stuck if developers can't reproduce the problem. If you can't read HTML, drive wget, and host the files, find someone on XSCE to help you? -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
