a hack around, posted by Andrey on Thu Dec 29 20:26:11 2022
|
FYI.
Removing "wrap=hard" on the line #11461 in the elogd.cxx file resolves my problem.
|
|
a hack around, posted by Konstantin Olchanski on Fri Dec 30 00:46:03 2022
|
- rsprintf("<textarea rows=%d cols=%d wrap=hard name=\"Text\">\n", height, width);
+ rsprintf("<textarea rows=%d cols=%d name=\"Text\">\n", height, width);
|
|
webkit bug, posted by Andrey Pashnin on Mon Jan 2 12:32:13 2023
|
FYI
They seem to have accepted the bug report:
|
|
a hack around, posted by Stefan Ritt on Wed Jan 4 09:33:25 2023
|
> - rsprintf("<textarea rows=%d cols=%d wrap=hard name=\"Text\">\n", height, width);
> + rsprintf("<textarea rows=%d cols=%d name=\"Text\">\n", height, width);
>
|
a hack around, posted by Stefan Ritt on Wed Jan 4 09:39:38 2023 
|
Ahh, now I remember. Well, the I put that in like 25 years ago ;-)
Let's assume the user write a very long line and relies on the wrapping of the text box. So the input might look like the
|
|
editing on a smartphone, posted by Andrey Pashnin on Wed Jan 4 10:05:38 2023
|
oh! so, that's the cause of another problem I faced a while ago.
When people edited an ELOG page on a narrow screen device (a.k.a smartphone) it put the extra CRLF and made the page look like the attachment below
(it broke the original formatting).
|
|
editing on a smartphone, posted by Stefan Ritt on Wed Jan 4 10:12:43 2023
|
Yepp, that's right. But without the "wrap=hard", you could get one single long line which is almost impossible to read. So there is no perfect solution
for all cases. I see three options
|
|
config option?, posted by Andrey Pashnin on Wed Jan 4 11:03:45 2023
|
How about adding a config option?
Ideally, it might be nice to have this option "per record" or "per logbook", but "per instance" should be good enough. |