Ameblo.jp - The top logo opens a blank page

NEW
Unassigned

Status

Tech Evangelism
Mobile
P1
normal
10 months ago
16 days ago

People

(Reporter: Oana Horvath, Unassigned, NeedInfo)

Tracking

Trunk
Unspecified
Android

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [sitewait], URL)

(Reporter)

Description

10 months ago
Devices:
- LG G4 (Android 5.1)
- Huawei Honor 8 (Android 6.0)

Build: Firefox 54.0.1

Steps to reproduce:
1. Go to ameblo.jp
2. Tap the "Ameba" logo on the top of the homepage.

Expected results: 
The signup page opens.

Actual results:
A blank page opens. The redirect to the signup page is not completed.

Notes: 
Not reproducing on Chrome.
Flags: webcompat?
Flags: webcompat?
Whiteboard: [needsdiagnosis]
Flags: needinfo?(kdubost)
Priority: -- → P1
Karl, can you take a look?

Comment 2

21 days ago
The top logo doesn't do anything on any browsers.
Maybe the site has changed.

There is a yellow banner currently which says
アメブロをはじめる(無料) (Start for free Ameblo)


ON CHROME

This happens.

1. http://lo.ameba.jp/v1/ORRTwLSZbEygjKxEnBKP
   302 to

2. https://s.amebame.com/#pre?from=blog&frm_id=v.logout_ameblo_top-register-ameba1
   200 OK
   a bunch of resources are loaded and I guess there is a JS initiated redirect to

3. https://s.amebame.com/oauth/ameba?state=register&style=am-blog&frm_id=v.logout_ameblo_top-register-ameba1_c.am-blog-blog-login 
   302 to

4. https://dauth.user.ameba.jp/authorize?state=register&frm_id=v.logout_ameblo_top-register-ameba1_c.am-blog-blog-login&style=am-blog&scope=profile%2Capplication%2Cconnection%2Cphoto%2Ccoin&response_type=code&client_id=db98bf8b687fc3334c4b8cde9116687fd75eb285ed5a2373df8010ae070f5338
   302 to 

5. https://dauth.user.ameba.jp/authenticate?client_id=db98bf8b687fc3334c4b8cde9116687fd75eb285ed5a2373df8010ae070f5338&redirect_uri=https%3A%2F%2Fdauth.user.ameba.jp%2Fauthorize%3Fstate%3Dregister%26frm_id%3Dv.logout_ameblo_top-register-ameba1_c.am-blog-blog-login%26style%3Dam-blog%26scope%3Dprofile%252Capplication%252Cconnection%252Cphoto%252Ccoin%26response_type%3Dcode%26client_id%3Ddb98bf8b687fc3334c4b8cde9116687fd75eb285ed5a2373df8010ae070f5338

   which is finally received with a 200 OK.


On FIREFOX

We fail at step 2. So the 200 OK is not going further because probably the JavaScript redirection fails.

And indeed in the console we can find.
08:39:04.003 [Show/hide message details.] InvalidAccessError: A parameter or an operation is not supported by the underlying object all.js:2816 (once prettified)

The line 2816 is the one with function (e) {


  $.dispatcher = new o;
  $.routes = $.dispatcher.routes
}) (window); /**
 * chikwua-view
 * Copyright (c) 2011 CyberAgent, Inc.
 * License: MIT (http://www.opensource.org/licenses/mit-license)
 * GitHub: https://github.com/suguru/chikuwa.js
 */
(function (e) {
  var t = $.log;
  var n = {
  };

If it's really the issue it's not the first time we have issues with chikuwa
https://github.com/ameba-proteus/chikuwa.js/issues/1
https://bugzilla.mozilla.org/show_bug.cgi?id=958415#c6 

Note that the last commit on this project was 5 years ago. 

The internal branch of chikuwa seems different.
as said in 

> * We cannot upgrade chikuwa.js on ameba.jp immediately because its internal branch is pretty different from the open sourced code.
> As for contact it also means there is probably 0 hope to change it on the original project. 
See https://bugzilla.mozilla.org/show_bug.cgi?id=958415#c20

And the only able who are able to affect a change there are the owners of ameblo.
We had success contacting them through chikoski in the past 
https://webcompat.com/issues/926


Ohzeki-san, this is another instance of failure in the login process of ameblo.jp
Flags: needinfo?(kdubost) → needinfo?(saneyuki.s.snyk)
Whiteboard: [needsdiagnosis] → [sitewait]
You need to log in before you can comment on or make changes to this bug.