Open webcompat-bot opened 3 years ago
Thanks for the report, I was able to reproduce the issue.
Note:
Console:
Tested with: Browser / Version: Firefox Nightly 92.0a1 (🦎 92.0a1-20210808090543), Firefox Beta 91.0.0-beta.6 (🦎 91.0-20210802134352) Operating System: Google Pixel 5 (Android 11) - 1080 x 2340 pixels, 19.5:9 ratio (~432 ppi density), Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density) VPN pointing to Japan
Moving to Needsdiagnosis for further investigation.
This is done through user agent sniffing. The issue can be reproduced in Firefox desktop with rdm mode and Firefox Android UA. If I switch the UA to be chrome in on RDM, I get the video working.
This is what Chrome is displaying:
<iframe
id="yvpubplayer0"
name="frame_yvpubplayer0_1628577914"
src="//s.yimg.jp/images/yvpub/player/vamos/sd/latest/player.html?contentid=4995710&height=223&width=395&propertyname=jp_news&recommend=0&spaceid=2079842558&autostart=0&repeat=0&quality=240&ds=88946_529603&id=yvpubplayer0&domain=news.yahoo.co.jp&parenturl=https%3A%2F%2Fnews.yahoo.co.jp%2Farticles%2Ff114c5451c4a8f18e4aeccaae8f57a1daaf597fa&parentfullurl=https%3A%2F%2Fnews.yahoo.co.jp%2Farticles%2Ff114c5451c4a8f18e4aeccaae8f57a1daaf597fa&_playersession=ed878271-7756-4f29-88a6-f9601e869458"
title="Yahoo!ビデオパブリッシャー"
scrolling="no"
style="display: block"
marginheight="0"
marginwidth="0"
allowfullscreen="true"
allow="autoplay; fullscreen"
data-yvpubviewablecheck="id0"
data-yvpubintersectionratio="1"
width="395"
height="222.1875"
frameborder="0"
></iframe>
They use videoJS inside the iframe.
The iframe is not triggered on Firefox Android and the error message is being displayed instead.
<script src="https://s.yimg.jp/images/yvpub/player/js/player.js?v=1628578065673"></script>
<div
class="yvpub-player yjads_priority_3"
data-contentid="4995710"
data-height="224"
data-width="398"
data-propertyname="jp_news"
data-recommend="0"
data-spaceid="2079842558"
data-autostart="0"
data-repeat="0"
data-quality="240"
data-ds="88946_529603"
style="
position: absolute;
top: 0px;
left: 0px;
width: 398px;
height: 224px;
vertical-align: middle;
text-align: center;
background-color: rgb(0, 0, 0);
overflow: hidden;
"
data-composed="1"
>
<div
id="yvpubplayer0"
data-key="yvpubplayer0"
style="
width: 398px;
height: 224px;
text-align: center;
position: relative;
z-index: 1;
margin: auto;
overflow: hidden;
vertical-align: middle;
cursor: pointer;
"
>
<div
style="
font-size: 14px;
z-index: 3;
color: rgb(255, 255, 255);
position: relative;
top: 82.5px;
"
>
<span style="font-size: 10px">エラーコード:1001100</span>
<div>
ご利用の環境では映像を視聴できません。<br />映像視聴における推奨環境はこちらをご確認ください。
</div>
</div>
</div>
</div>
Let's look at
https://s.yimg.jp/images/yvpub/player/js/player.js?v=1628578063801
Ah hard to debug because they create a parameter based on Epoch time in milliseconds at each new request:
https://s.yimg.jp/images/yvpub/player/js/player.js?v=1628578616434 https://s.yimg.jp/images/yvpub/player/js/player.js?v=1628578698956
There is a function UnsupportedEnvironment
UnsupportedEnvironment: function () {
var e = a.isSmartDevice() ? o.commonConfig.HELP_URL.SD : o.commonConfig.HELP_URL.PC,
n = t && t.noLink ? 'こちら' : '<a href="' + e + '" class="vjs-error-help-link" target="_blank">こちら</a>';
return new u.default({
code: 1001100,
headline: 'ご利用の環境では映像を視聴できません。',
message: '映像視聴における推奨環境は' + n + 'をご確認ください。',
options: t
})
}()
but it is quite simple. Their support matrix is just not considering Firefox Android.
W = {
PC: {
Windows: {
VERSION: 7,
BROWSER_LIST: [
{
NAME: 'Chrome',
VERSION: 31
},
{
NAME: 'Firefox',
VERSION: 45
},
{
NAME: 'Edge',
VERSION: z = 'ANY'
},
{
NAME: U = 'ChromiumEdge',
VERSION: z
},
{
NAME: 'IE',
VERSION: 11
}
]
},
'Mac OS': {
VERSION: z,
BROWSER_LIST: [
{
NAME: 'Chrome',
VERSION: 31
},
{
NAME: 'Firefox',
VERSION: 45
},
{
NAME: U,
VERSION: z
},
{
NAME: 'Safari',
VERSION: 8
}
]
}
},
SD: {
iOS: {
VERSION: 10,
BROWSER_LIST: z
},
Android: {
VERSION: 4.4,
BROWSER_LIST: [
{
NAME: 'Chrome',
VERSION: 53
},
{
NAME: U,
VERSION: z
},
{
NAME: 'Silk',
VERSION: z
},
{
NAME: 'Samsung Browser',
VERSION: z
},
{
NAME: 'Facebook',
VERSION: z
},
{
NAME: 'Line',
VERSION: z
},
{
NAME: 'Instagram',
VERSION: z
}
]
}
}
},
Let's add it to ua override.
Site Interventions request at https://bugzilla.mozilla.org/show_bug.cgi?id=1724868
The current sitepatch only applies to Yahoo(jp) News, but this Firefox-eliminating video player is also used by at least the following sites.
https://movies.yahoo.co.jp/
https://soccer.yahoo.co.jp/ws/
(android only)https://sports.yahoo.co.jp/
https://tv.yahoo.co.jp
https://weather.yahoo.co.jp/weather/video/
Thanks @hokonch.
Lets try @yahoojapan. Maybe @kpango could help us with this issue. Hi Yusuke, we're wondering what could be a reason for not supporting Firefox on mobile here. Would you be able to pass this along to the relevant person or team to be looked at? Thank you!
@myakura do you still have contact with Yahoo! Japan?
Hey @karlcow,
@myakura do you still have contact with Yahoo! Japan?
I don't know. But I can ask :)
So far, If I'm reading it right, the current situation is:
Let me know if there's anything wrong in the points I made, or any other things you want to tell.
Let me know if there's anything wrong in the points I made, or any other things you want to tell.
Not @karlcow, but yes, your points are correct @myakura :)
One thing I wanted to add is, right now we only have Chrome UA intervention only for https://news.yahoo.co.jp/
, but as @hokonch mentioned the issue is affecting a lot more subdomains. While we could ship this intervention for all subdomains (essentially *.yahoo.co.jp
), that would be less than ideal as it can cause other issues that we are not aware of and Firefox will disappear from Yahoo japan browser usage statistics (if they have any).
Hello @ksy36 ,
Not @karlcow, but yes, your points are correct @myakura :)
Yay ;)
One thing I wanted to add is, right now we only have Chrome UA intervention only for
https://news.yahoo.co.jp/
, but as @hokonch mentioned the issue is affecting a lot more subdomains.
Ah. Okay.
While we could ship this intervention for all subdomains (essentially
*.yahoo.co.jp
), that would be less than ideal as it can cause other issues that we are not aware of and Firefox will disappear from Yahoo japan browser usage statistics (if they have any).
Agreed.
I just sent them a message (pointing to this thread and bugzilla entry). Hopefully getting back soon.
Hi, all. I'm an engineer at Yahoo! JAPAN. Thank you for raising this issue.
The player you mentioned is a web player used in all of Yahoo! Japan's services.
It seems that this player judges which browsers can play based on UA, and treats all others as errors. I will contact the engineer who is creating the player about this issue.
Great, thanks a lot @myakura and @narirou :)
Updated link: https://news.yahoo.co.jp/pickup/6423826
Updated link: https://news.yahoo.co.jp/articles/0f78ab97ea915c0f3f6d3184d67b124cd52fa534
[inv_40/2022]
URL: https://news.yahoo.co.jp/articles/841aaa7adca87e4c7b180917ff8da868d227d924
Browser / Version: Firefox Mobile 91.0 Operating System: Android 11 Tested Another Browser: Yes Chrome
Problem type: Site is not usable Description: Browser unsupported Steps to Reproduce: The videos provided by Yahoo! JAPAN don't play in browsers running on Fenix or Linux browsers.
Yahoo News is one of the most high-traffic websites in Japan.
Yahoo Japan deletes their articles in about two weeks. You can access the latest video news here
The support policy for their video player
View the screenshot
Browser Configuration
View console log messages
From webcompat.com with ❤️