www.lovoo.com - design is broken

[webcompat-bot]

URL: https://www.lovoo.com/

Browser / Version: Firefox Mobile 59.0
Operating System: Android 8.1.0
Tested Another Browser: No

Problem type: Design is broken
Description: chat window is unusable, and profiles are buggy
Steps to Reproduce:

From webcompat.com with ❤️

[MDTsai]

Design is the same for me using Chrome/Firefox mobile. There is one error message while click chat:

Error: e.response is undefined
a@https://webassets.lovoo.com/js/lovoo.min.js?1513870906374:1:277734
d/</k[o]/S<@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:483394
s/<@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:359839
$eval@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:367149
$digest@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:365706
$apply@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:367445
m/<@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:344140
g@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:345535
pt/</w.onload@https://webassets.lovoo.com/js/external.min.js?1513870906374:1:346081

[softvision-sergiulogigan]

Well, this is something interesting...
It seems that when using the Chat and sending a message, you get logged out.

Console says:

[karlcow]

when POSTING The message we get

HTTP/2.0 403 Forbidden
date: Wed, 22 Aug 2018 04:50:49 GMT
content-type: application/json; charset=utf-8
content-length: 2
cache-control: max-age=0, must-revalidate, no-cache, no-store, private
set-cookie: lovoo=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=.lovoo.com; secure; httponly
lovoocsrf=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=.lovoo.com; secure
LooCoo=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=.lovoo.com; secure; httponly
lovoo=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT; secure; httponly
via: 1.1 google
alt-svc: clear
strict-transport-security: max-age=15552000
x-content-type-options: nosniff
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 44e2b87fcc7d9481-NRT
X-Firefox-Spdy: h2

The POST data were

{"text":"test me what is happening","userId":"5473043ccd6da1f4618b4595"}

and the request

POST /api/users/5473043ccd6da1f4618b4595/write HTTP/1.1
Host: www.lovoo.com
User-Agent: Mozilla/5.0 (Android 7.0.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0
Accept: application/json, text/plain, */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://www.lovoo.com/list/liked-you
APP: lovoo
Content-Type: application/json;charset=utf-8
X-Csrf-Token: wQAhAYAdNPtVvnHSJysY6950
Content-Length: 72
Connection: keep-alive
Cookie: ****

and it's not about the user agent.

@softvision-sergiulogigan did it work for you on Chrome?

[softvision-sergiulogigan]

Hey @karlcow

Tested on Samsung Galaxy S6, Android 7.0, 1440 x 2560 pixels (~577 ppi pixel density).
On Nightly with Chrome UA, the Logout action is still performed after sending a message.
On Chrome, on the other hand, no Logout action is performed after sending a message.

Chrome 68:

[karlcow]

ah on Chrome I get a 403 too with exactly the same type of request and response.
So it is really done to how the response is handled by each browser.

[karlcow]

fwiw this is happening on firefox desktop too.

[karlcow]

I'm also suspicious about this error message

reCAPTCHA couldn't find user-provided function: vcRecaptchaApiLoaded

<script async type="text/javascript" src="https://www.google.com/recaptcha/api.js?onload=vcRecaptchaApiLoaded&render=explicit&hl=en"></script>

This should probably be rewritten as

<script async type="text/javascript" src="https://www.google.com/recaptcha/api.js?onload=vcRecaptchaApiLoaded()&render=explicit&hl=en"></script>

aka vcRecaptchaApiLoaded() instead of vcRecaptchaApiLoaded.

but probably not related to our issue. :/

[karlcow]

@denschub an idea?

[karlcow]

Taking another shot.

lovoo is coded with angular. I checked if there was something about vcRecaptchaApiLoaded
And I found that some people had the same issue.

and indeed the solution to this is the one in my previous comment

<textarea
  messenger-textarea=""
  content="selectedConversation.newMessageContent"
  on-first-char="firstCharTyped()"
  on-change-height="changedTextareaHeight(height)"
  on-enter="pressedEnterInTextarea()"
  max-rows="5"
  rows="1"
  class="small padding no-border full-width overflow-y-hidden"
  ng-class="{'bg-body': !selectedConversation.requestHelper.messages.isLoaded}"
  ng-disabled="!selectedConversation.requestHelper.messages.isLoaded"
  placeholder="Ton message"
  data-automation-id="new-chat-message-textarea"
  style="height: 39px;"
>
</textarea>

Let's see on Chrome.

So I guess this is not working in Chrome too.
The only difference is that it doesn't log out and it doesn't try to redirect to the home page.

to note that the URI at the top is
https://www.lovoo.com/welcome/login

Also funny thing, my interactions with the site seems to work better in general in Firefox than in Chrome. I got logged out during one interactions with Chrome too.

            responseError: function (n) {
              var l,
              c;
              if (0 === n.status) return n;
              if (403 === n.status && 'Forbidden' === n.statusText || n.access_denied) return a.location.href = o.Ajax.url + '/?show_login=true';
              if (429 === n.status && n.data) {
                var d = t.get('DialogService');
                return void d.openHtml(n.data)
              }

We are in the case of

 if (403 === n.status && 'Forbidden' === n.statusText || n.access_denied) return a.location.href = o.Ajax.url + '/?show_login=true';

And this is the part which is activated when we send a message

        o.sendMessage = function () {
          if (u.reinitialise(), !o.selectedConversation.sendMessage()) return;
          g = !1,
          o.$broadcast('messenger-textarea-focus'),
          o.selectedConversation.isRequest && function () {
            if (!o.selectedConversation.isRequest) return;
            var e = o.conversationLists.request.conversations.indexOf(o.selectedConversation);
            o.conversationLists.request.conversations.splice(e, 1),
            o.selectedConversation.isRequest = !1,
            _.each(o.conversationLists.active.conversations, function (e) {
              e.isSelected = !1
            }),
            o.conversationLists.active.conversations.unshift(o.selectedConversation),
            o.selectConversationList('active'),
            v(!1)
          }()
        },

and this is probably happening here

          if (u.reinitialise(), !o.selectedConversation.sendMessage()) return;

let's move this to needscontact.

[karlcow]

and fwiw this is not mobile only. This is happening on Desktop too.

[softvision-sergiulogigan]

This is still happening.

Tested with:
Browser / Version: Firefox Preview Nightly 191031 (🦎: 72.0a1-20191029093803)
Operating System: Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density)

[cipriansv]

After retesting the issue I confirm that the issue has been fixed.

After sending a text message you are nor logged out, you receive a prompt containing a message.

Tested with:
Browser / Version: Firefox Nightly 200824(🦎 81.0a1-20200820093209)
Operating System: OnePlus6 (Android 10) - 1080 x 2280 pixels (~402 ppi pixel density)

Closing the issue as fixed.