SRWare.net

bugman wrote:still unable to post replies and top level comments on youtube. hopefully this will get fixed in the next version or maybe someone can find a workaround.
also tried changing the useragent and disabling all extenstions and multiple combinations of both, with no effect. same issue everytime. The G+ window comes up, I log in, the page refreshes but doesn't give me the ability to enter text in the comment boxes.

I can also confirm vine videos and the vine homepage are not working optimally.


On a happier note, spotify seems to have gained some stability

RazerAnansi wrote:

bugman wrote:still unable to post replies and top level comments on youtube. hopefully this will get fixed in the next version or maybe someone can find a workaround.
also tried changing the useragent and disabling all extenstions and multiple combinations of both, with no effect. same issue everytime. The G+ window comes up, I log in, the page refreshes but doesn't give me the ability to enter text in the comment boxes.

I can also confirm vine videos and the vine homepage are not working optimally.


On a happier note, spotify seems to have gained some stability

Just logged in and posted on Youtube with no problem with 39 portable. Are you able to post using another browser. Were you able to post on Youtube from a previous version of Iron. Do you have 3rd party cookies blocked. YouTube is a 3rd party ! Try this

→ Chrome menu (≡ or wrench) → "Settings"
in the box "Search settings" → type "cookies" (without quotes)
under "Privacy" → "Content settings"
under "Cookies" → either uncheck "Block third-party cookies" → "Close"
or
check "Block third-party cookies and site data" → "Manage exceptions"
under "Hostname pattern:" → type "youtube.com" (without quotes) → ''Allow"
also type "google.com" (without quotes) → "Allow"
→ "Done" → "Close"

RESTART Iron and see what happens. Hope it helps.

Comment #16 on issue 429452 by fabian.r...@gmail.com: Purchased youtube video plays in chrome but not in chromium (correct .gyp settings & identical version)
https://code.google.com/p/chromium/issu ... ?id=429452

I am the original person filing the bug: I've fixed it in the mean time. It's just a few gyp flag changes and simple modifications to the gyp files. It will take some time until I can post a clean diff but here are the things I remember:

1) build with the following gyp flags:
ffmpeg_branding='Chrome', proprietary_codecs=1, enable_pepper_cdms=1, enable_webrtc=1

2) Uncomment the version number and strings in src/third_party/widevine/cdm/widevine_cdm_common.h and change it to which ever binary version you have available. I installed the vanilla google-chrome debian package from Google and used the version string and number found in chrome://plugins/

3) in the same folder modify widevine_cdm.gyp. Change 'branding == "Chrome"' to 'branding == "Chromium" in line 10 and 88 (not sure if this is really necessary)

4) When compiling Chromium it will complain about a missing widevine binaries folder (can't remember where it was meant to be located). Create it and copy the binaries over from chrome. It will also complain about missing widevine_cdm_version.h and/or widevine_cdm_common.h. Just copy widevine_cdm_common.h you edited above to the location expected by the build system.

5) after building, test by watching purchased video on youtube and/or netflix. If we are packaging this as open source (for debian for example), remove the widevine binaries from the out/Release folder and create another non-free package just for the widevine binaries as is being done for pepperflash.

I'm sorry for not providing a patch for this but I am travelling on a netbook with limited resources and creating a patch and testing it would take weeks of compiling.

Hope this helps!