nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Inconsistency of input drops + ai behaviour

Darkknight_94

I am not gonna type all that.. again.
Hence putting the screenshot for interpretation.

Comments

Darkknight_94

Feel like they doesn't care about this topic anymore & ignores it swiftly

TheParasite

mate, as a software engineer myself, i could say one thing about this, the factors that cause the dropped inputs
the number of data stored in the RAM (from background screens to buffered animation so on) of the device at that moment, the touch sensitivity of the touchscreen and the delayed input response of the touch, which may get clogged at some times and if one input gets delayed and the next tries to enter, both the inputs fail or either one of it gets activated and the other fail.
the main problem is anyone cannot recreate the situation of happening. Its a very tough cookie to crack,
there might be a possible solution of reducing the animations or clearing the data of a screen when we switch to other screen. but the problem with that is when we hit back, it takes a ton of time to load everything from the previous screen again. and our device OS is also mainly involved in it, either ios or android it tends to clear data when the ram is almost 80% used from the allocation for an app. that will again cause the delay which ignores the input, that time when it tries to do it. hopefully they do find a good solution for it asap. fingers crossed