1378726 - Ameblo.jp - The top logo opens a blank page

Status: RESOLVED FIXED

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

Description

[Oana Horvath [:ohorvath]]

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.

Comment 1

[Mike Taylor [:miketaylr]]

Karl, can you take a look?

Comment 2

[Karl Dubost💡 :karlcow]

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

Comment 3

[Tetsuharu OHZEKI [:tetsuharu] (UTC+9)]

(In reply to Karl Dubost :karlcow from comment #2)
> Ohzeki-san, this is another instance of failure in the login process of
> ameblo.jp


I apologize that this reply was late.

Just like https://bugzilla.mozilla.org/show_bug.cgi?id=958415#c20,I heard summaries of the current status from my colleague:

* The status of chikuwa.js is not changed from https://bugzilla.mozilla.org/show_bug.cgi?id=958415#c20.
* We're working to replace the part using chikuwa.js with more standard ways. When we finished its work, we hope this compat issue would be fixed.
    * We plan to ship this effort from the later of this year. However, we don't have any concrete plan which we can make public.

This is the current status of this issue.
I'm sorry to we cannot report a good news.

Comment 4

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Comment 5

[Raul Bucata]

I was not able to reproduce the issue. Tapping on the logo redirects me to the ameba.jp sign-up page:

https://prnt.sc/JlAeIzBCGpxo

Oana, could you please confirm this?

Tested with:

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

Comment 6

[Oana Horvath [:ohorvath]]

Can confirm it works fine now. Thanks.