Closed
Bug 1482300
Opened 8 years ago
Closed 2 years ago
https://vreplay.mozilla.com/replay/login.html text entry is janky and loses characters
Categories
(Infrastructure & Operations Graveyard :: AVOps: Vidyo, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mozbugz, Unassigned)
Details
Go to https://vreplay.mozilla.com/replay/login.html and try to login.
While typing my username or password, entry would sometimes freeze, and in fact completely ignore my keypresses for a second or two.
This made entering my password pretty much impossible (not knowing if my characters were all there), and I had to type it elsewhere and paste it to be able to login!
Google Chrome seems less janky, and at least doesn't lose any characters (they all appear at once after the freezing stops).
MS Edge is almost jank-free, and doesn't lose characters either.
Since the freezes appear on all browsers, I put this bug in airmo->vidyo.
But if the loss of characters is a Firefox-only bug, maybe it should move to core->layout: form controls?
Firefox Nightly, seen on WIndows 10 and Mac OS X 10.13.6 (didn't try on Linux).
Comment 1•7 years ago
|
||
I hit this today too.. quite annoying
Comment 2•7 years ago
|
||
Please change this to a Vidyo product issue - not AirMozilla.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Comment 3•7 years ago
|
||
How do we do that? Which Bugzilla component is responsible for our instance of Vidyo?
| Reporter | ||
Comment 4•7 years ago
|
||
Discussed with Andy, we can change the component to AVOps:Vidyo.
Status: RESOLVED → REOPENED
Component: Vidyo → AVOps: Vidyo
Product: Air Mozilla → Infrastructure & Operations
Resolution: INVALID → ---
Version: unspecified → Production
Comment 5•2 years ago
|
||
Closing this bug as Vidyo is no longer used and this component will be archived.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 2 years ago
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•