jow-
commented
2 years ago I assume that this issue is not present anymore.
Closed wpwrak closed 2 years ago
jow-
commented
2 years ago I assume that this issue is not present anymore.
When using my workstation, input fields that default to a drop-down list with a "-- custom --" item to turn them into a text input field don't work for me. All that happens after I select "-- custom --" is that the page briefly changes (it happens too fast to tell to what exactly, but it's usually either a vertical jump by a few pixels or fields moving horizontally), but immediately reverts to the original state.
Example: the "IPv4-Address" field in Network > DHCP and DNS > General Settings > Static Leases.
Input fields that don't have a drop-down list of choices work fine.
System environment:
I tried with the same result from another PC running a fresh Chromium installation (same version, no extensions) on Ubuntu 18.04.2 LTS.
Using Firefox on my Android phone did work, however. After some experimenting, I tried changing the window manager. I normally use fvwm2. For the window manager experiments I used Xnest. Chromium performed there, under fvwm2, exactly like on my regular desktop. An attempt with ancient twm went worse: the drop-down list only opened briefly, to disappear instantly, not giving me any opportunity to select "-- custom --".
Then I tried i3: magically the problem disappeared, and the input field changed to text input. So LuCI somehow manages to be affected by the window manager, and that across two different browsers (i.e., Chromium and Firefox).
Further experiments revealed that the text-based ELinks browser would also produce correct behaviour.
Last but not least, back in my regular setup with Chromium and fvwm2, I set an Event Listener Breakpoint on Control/change. Surprisingly, this also made the change to a text field work. (After continuing from the breakpoint.)
Summary: in the case of input fields with a drop-down list, LuCI seems to have some dependency on the events the window manager generates, or their sequence. The result is that the input field cannot be changed to a "custom" text field. This can be observed, with different symptoms, with twm and fvwm2. This behaviour can be reproduced in Xnest.