1020740 - sp.nhknews.jp/sp/ blocks smartphone browser which are not iOS or Chrome Android

Status: RESOLVED INVALID

(Web Compatibility :: Site Reports, defect, P3)

Description

[Karl Dubost💡 :karlcow]

Site: http://sp.nhknews.jp/sp/index.php
sp.nhknews.jp/sp/ blocks smartphone browser which are not iOS or Chrome Android

:: Steps To Reproduce

1. With Firefox Android, UCWeb, Opera Android
2. Go to http://sp.nhknews.jp/sp/index.php


:: Expected Result

Display the Web site for smartphone

:: Actual Result

There is a blocking message saying it is not supported.

:: Additional Information

Software Version: 30
Device Information: GT-i9100
Reporter's User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0

Comment 1

[Karl Dubost💡 :karlcow]

# When using Firefox for Android or Opera Android or UCWeb Android

→ http --print hH GET http://www.nhknews.jp/index.html "User-Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0"
GET /index.html HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: www.nhknews.jp
User-Agent:  Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0

HTTP/1.1 302 Found
Location: http://sp.nhknews.jp

Then 

HTTP/1.1 302 Found
Location: http://sp.nhknews.jp/sp/index.php

Then

HTTP/1.1 302 Found
Location: http://sp.nhknews.jp/sp/NotSupport.php

Then 

HTTP/1.1 200 OK
Content-Length: 2471
Content-Type: text/html; charset=Shift_JIS

Comment 2

[Karl Dubost💡 :karlcow]

Another subtlety in the menus with the cascade

in style.css
nav#pageNav ul li a {
    color: rgb(255, 255, 255);   // <- white
    font-size: 16px;
    display: block;
    text-align: center;
    border-radius: 2px;
}

in default.css
a:link {
    color: rgb(23, 88, 175);  // <- blue
}

style.css has precedence over default.css and we get a white on white text.
But this is happening because the blue linear gradient is not applied because it is webkit only. 
Two things that could be done. Specify a default background color which is not white. Better convert the gradient to a standard value.

Comment 3

[Karl Dubost💡 :karlcow]

ok the blocking is not only dependent on Android Chrome. Some of them will be blocked too. 
It depends if the phone is known from one of the three majors operators in Japan.
The reason is that the billing is done through these operators. It's a paywall.

I propose we close this as WONTFIX, until/if one day we have  a deal with one operator in Japan.

Comment 4

[Karl Dubost💡 :karlcow]

See details in https://bugzilla.mozilla.org/show_bug.cgi?id=1020747#c1

Comment 5

[Karl Dubost💡 :karlcow]

Attachment: nhk.png

The screenshot of the message.

Comment 6

[Karl Dubost💡 :karlcow]

Attachment: nhk-fake-chrome-ua.png

On Gecko with Fake Chrome UA.
No need for webkit fix anymore. It's working with standard properties.

I wonder if we should try to recontact them.

Comment 7

[Karl Dubost💡 :karlcow]

Though any secondary articles are dependent on registration, but credit cards are accepted.
https://sp.nhknews.jp/sp/user/RegistSp.php

Comment 8

[Adam Stevenson [:adamopenweb]]

Karl - is this still an issue we should pursue?

Comment 9

[Karl Dubost💡 :karlcow]

We should add a UA override for this Web site. 
I don't think any contact will work. We tried in the past.

> お使いの機種では本サービスをご利用頂けません。
> 
> 本サービスはAndroidの標準ブラウザ、もしくはiPhoneの場合はSafariからのご利用をお願いしております。
> Androidの標準ブラウザ及びiPhoneのSafari以外をお使いの場合、この画面が表示される場合があります。

It is still send this message. which says basically that you need to use an Android default browser or Safari on iPhone. 

Note that if you give it a Chrome User Agent string, the same thing is happening.
The only string which is working for me is the iPhone UA string.


For example
    Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.4.6 (KHTML, like Gecko) Version/10.0 Mobile/14D27 Safari/602.1


I'll give it a last shot by email. If it doesn't work, I propose we override the UA string.
Or maybe we can try to see if someone in Google Japan can help us influence their choice. 


Firefox Android

GET /sp/index.php HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: sp.nhknews.jp
User-Agent: Mozilla/5.0 (Android 7.0.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0

HTTP/1.1 302 Found
Connection: Keep-Alive
Content-Length: 0
Content-Type: text/html; charset=Shift_JIS
Date: Fri, 03 Aug 2018 00:10:41 GMT
Keep-Alive: timeout=5, max=100
Location: https://sp.nhknews.jp/sp/NotSupport.php
Set-Cookie: TS01742239=012d2e201ac6b23f95813bdf52b34ac5cf4a95febd893323f3fd531af0deb3de0315945edf766fec5e9ab26354bbc182f4bcce6243; Path=/



iPhone UA string

GET /sp/index.php HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: sp.nhknews.jp
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.4.6 (KHTML, like Gecko) Version/10.0 Mobile/14D27 Safari/602.1

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Type: text/html; charset=Shift_JIS
Date: Fri, 03 Aug 2018 00:11:26 GMT
Keep-Alive: timeout=5, max=100
Set-Cookie: TS01742239=012d2e201a011b78790f573da3140ec2e922d8eb32894d6b7e75187a79562082954b28c9eac9d5836efc2cef82a1a9567e5ac3a470; Path=/
Transfer-Encoding: chunked

Comment 10

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 11

[Raul Bucata]

The page can not be accessed via Firefox due to security concerns regarding the certificate, but Chrome can pass the warning, and a message saying that the page is not available anymore is displayed (end of service)

https://prnt.sc/vYYnyHmEzuRX

Karl is it safe to say that we can close this issue, since the page is not available?

Tested with:

Browser / Version: Firefox Nightly 100.0a1 (2015869419 -🦎100.0a1-20220317092857🦎)/Chrome Mobile Version 99.0.4844.73
Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)

Comment 12

[Karl Dubost💡 :karlcow]

Yes this became invalid since the site is not available anymore.