touch-packages team mailing list archive

[Launchpad Bug Tracker <1412880@xxxxxxxxxxxxxxxxxx>]

** Branch linked: lp:ubuntu/vivid-proposed/webbrowser-app

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1412880

Title:
  Videos on youtube.com won’t play on desktop

Status in Web Browser App:
  In Progress
Status in oxide-qt package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Currently the Youtube webapp fails to play any videos on desktop with
  Oxide 1.4. When I try it, I see messages like this in the console:

  qml: [JS] (https://www.youtube.com/watch?v=LHp3jqRj-jg:0) Mixed
  Content: The page at 'https://www.youtube.com/watch?v=LHp3jqRj-jg' was
  loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint
  'http://r14---sn-
  aigllnll.googlevideo.com/videoplayback?sver=3&dur=125.689&keepalive=yes&pl=22&mm=31&source=youtube&ms=au&id=o-ADWHdIzIFF9WjrfoIgjyExn9jZdvxCO_PDTaIVXhBrVg&mv=m&gir=yes&sparams=clen%2Cdur%2Cgir%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Ckeepalive%2Clmt%2Cmime%2Cmm%2Cms%2Cmv%2Cnh%2Cpl%2Csource%2Cupn%2Cexpire&signature=4B4BBAA1D31CA17FCCE5335993B871B5956AC835.44560638C7074E5FA66D5FE527DC9C9209BED319&lmt=1421740881545280&key=yt5&ip=95.172.233.148&upn=_oLxNA9ib50&itag=140&nh=IgpwcjAzLmxocjE0KgkxMjcuMC4wLjE&fexp=900238%2C900718%2C907263%2C927622%2C929305%2C931358%2C9405520%2C941004%2C943917%2C947209%2C947225%2C948124%2C948703%2C949422%2C952302%2C952605%2C952901%2C955301%2C957103%2C957105%2C957201%2C959701&expire=1421794356&ipbits=0&clen=2018474&mt=1421772625&mime=audio%2Fmp4&initcwndbps=982500&cpn
  =tczzNCjta-
  UMPRmn&alr=yes&ratebypass=yes&c=WEB&cver=html5&range=0-65535'. This
  request has been blocked; the content must be served over HTTPS.

  This is an expected change - Blink now treats XHR as active content
  instead of inactive content, so it gets blocked by the mixed content
  blocker.

  Changing the user agent string to the Chrome one seems to make it work
  again, so this will require a corresponding update to webbrowser-app
  with a user agent string override

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1412880/+subscriptions