[jitsi-dev] Unable to join a room containing a '


#1

Hello everybody,

I'd like to report what seems to be a bug :

Steps to reproduce :

- Go to meet.jit.si
- Enter a conversation name containing a ' character (for example,
something like "d'artagnan" causes the bug) and validate

Expected result :
Joining the conversation normally, or a message explaining that I chose
an illegal room name.

Actual result :
I join the room, but the conference is not working. I constantly get
popups indicating "focus.meet.jit.si not available - retrying in x
seconds", and the main window stays grey (But I can see my own face in
the bottom-right corner of the screen).

System informations :
- Fedora 25
- Firefox 54.0 (64-bit) (Note that I could reproduce the issue with a
clean Firefox profile, no add-ons or anything)

Since I'm not hosting this instance of Jitsi myself, I can't provide
either version number or logs. However, if someone wants me to try to
reproduce the issue against another instance, I'll be glad to help !

I couldn't find any open bug on the issue tracker about this, do you
guys want me to open one ?

···

--
Arnaud


#2

Hi,

Thanks for the report, we will take a look.

Regards
damencho

···

On Sat, Jul 22, 2017 at 11:16 PM, Arnaud Venturi <arnaud.venturi@rez-gif.supelec.fr> wrote:

Hello everybody,

I'd like to report what seems to be a bug :

Steps to reproduce :

- Go to meet.jit.si
- Enter a conversation name containing a ' character (for example,
something like "d'artagnan" causes the bug) and validate

Expected result :
Joining the conversation normally, or a message explaining that I chose
an illegal room name.

Actual result :
I join the room, but the conference is not working. I constantly get
popups indicating "focus.meet.jit.si not available - retrying in x
seconds", and the main window stays grey (But I can see my own face in
the bottom-right corner of the screen).

System informations :
- Fedora 25
- Firefox 54.0 (64-bit) (Note that I could reproduce the issue with a
clean Firefox profile, no add-ons or anything)

Since I'm not hosting this instance of Jitsi myself, I can't provide
either version number or logs. However, if someone wants me to try to
reproduce the issue against another instance, I'll be glad to help !

I couldn't find any open bug on the issue tracker about this, do you
guys want me to open one ?

--
Arnaud

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev