qlover.jp - Unsupported browser when playing videos
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Score:3, Webcompat Priority:P2)
People
(Reporter: railioaie, Assigned: twisniewski)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
(Keywords: leave-open, webcompat:site-report, webcompat:sitepatch-applied, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:blocked configuration:general affects:all branch:release diagnosis-team:webcompat user-impact-score:200
Attachments
(1 file)
Environment:
Operating system: Windows 11
Firefox version: Firefox 135.0
Preconditions:
Clean profile
Steps to reproduce:
- Navigat to: https://qlover.jp/portal/videos
- Select a video
- Observe
Expected Behavior:
The video is playing
Actual Behavior:
The video does not play
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/148271
![]() |
||
Updated•20 days ago
|
Comment 1•20 days ago
|
||
The error message says "This browser is not supported". Doesn't work with Chrome Mask, so we'd need to dig more.
Assignee | ||
Comment 2•20 days ago
|
||
This is another nicochannel site, as seen in bug 1844503. If we resolve this, it will likely resolve the blockage in the related sites for which our existing intervention is currently broken.
Updated•19 days ago
|
Updated•19 days ago
|
Comment 3•13 days ago
|
||
(In reply to Dennis Schubert [:denschub] from comment #1)
The error message says "This browser is not supported". Doesn't work with Chrome Mask, so we'd need to dig more.
For reference, the actual Japanese text shown on the site is:
このブラウザはサポートされていません。
That string appears twice in their source files (from searching devtools debugger for that text). The relevant match for this video is:
https://qlover.jp/assets/VideoDescription-0d8f6b4f.js
If you view that JS file directly, the glyphs are encoded differently for some reason, so find-in-page won't find them. The relevant snippet shown in DevTools (with the encoding of the glyphs that I quoted above) is:
xi = ({
thumbnailUrl: e
}) => {
const t = Mi();
return h(
'div',
{
className: t.container,
children: [
i(ft, {
src: e,
aspectRatio: ht.SIXTEEN_TO_NINE,
block: !0
}),
i(
'div',
{
className: t.absoluteCenter,
children: i(
G,
{
variant: 'body1',
color: 'inherit',
noWrap: !0,
className: t.desc,
children: 'このブラウザはサポートされていません。'
}
)
}
)
]
}
)
},
Assignee | ||
Updated•12 days ago
|
Assignee | ||
Comment 4•12 days ago
|
||
Updated•12 days ago
|
Comment 6•12 days ago
|
||
Backed out for causing failures at browser_interventions.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/a5f31fde35ddbb02b23fc5aef0f9d4df2bd6214b
Failure log: https://treeherder.mozilla.org/logviewer?job_id=496740708&repo=autoland&lineNumber=11514
Comment 9•11 days ago
|
||
bugherder |
Assignee | ||
Updated•11 days ago
|
Updated•10 days ago
|
Assignee | ||
Updated•10 days ago
|
Updated•8 days ago
|
Description
•