"Wordstringtext" New incompatibility emerged with certain websites and OpenWeb comment service
"Wordstringtext", New incompatibility emerged with certain websites and OpenWeb comment service. I have contacted both but have not received the courtesy of a reply. [yet]
First week of September 2022, suddenly a new problem emerged. First discovered at the Fox News website, when entering a comment (OpenWeb). The space between the last letter of the word before the first letter of the next word gets immediately deleted up on typing the next word. The end result is a text "band-worm" with no spaces. Another issue is that there is now suddenly a lengthy blank space (several scrolls) between the article and at the comment section.
Example of entering text: e.g. "this text entered here to make a comment appears as "thistextenteredheretomakeacomment".
Also unlike before, when pressing <space-bar> it limits to 1 space and you cannot add another i.e. double or more spaces. Once you begin typing upon entering the first letter of a word following the space, the cursor skips one character back eliminating the space. Laptop which OS and Firefox and noticed the same problem. Office computer the same problem. The issue apparently does not appear in chrome and/or edge. I can confirm that the problem can be reproduced with FF version 88 throughout to 10X & WaterFox all up to G4.1.5.
I suspect that "OpenWeb" saw the need to "update" something again. However, hoping to get a reply from their virtually non-existing support is like bringing a dead dog back to life by beating it. A futile attempt at best.
PS in the week with this problem suddenly appeared no "updates" of any kind where [willingly & knowingly] done on any system.
PPS Please no replies suggesting I try upgrade Firefox to whatever latest current. I tested all. I need a stable and reliable solution and not constantly a "Shove-it-down-your-throat-whether-you-want-or-like-it" new introduction of incompatibilities et al wasting my time and crippling my work flow.. It is this narco style "update mania" that creates all these totally unnecessary problems.
Constant "Upgrades" --the "Fentanyl" or food with sugar lacing of everything.
การตอบกลับทั้งหมด (9)
I haven't come across the problem. The solution apparently is to type a character like a period/full stop after the first backspace, then move back before that character and resume typing.
You can consider to use the Firefox 91.13.0 ESR version if you really want an old version.
Firefox 91.13.0 ESR:
We have seen reports that Openweb has fixed this issue and that it should now work properly. You may have to reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Thank you for your reply, I will try that. However, as of yesterday evening (~9pm PDT) it did not work and still produced the same error. Amongst other things also that all posts are also still double spaced. no single spaced lines possible. What used to be after two or three lines a "...see more" link is also gone and the double spaced text shows now the full length comment writing all doublespaced of course unless the sentence exceeds the maximum comment box width. then it wraps around/continues as single line spaced. Everything else is always doublespaced. any paragraph entry <enter> is published doublespaced yet when going back to edit it is singlespaced. lastly, since a couple of months there is also this huge white space (1 or 2x page down) between the article and and the comment section begin header. I will see what happens on Monday and will post my findings here.
PS OpenWeb is pretty much hiding under a rock when it comes to being able to contact their apparently and evidently none existing support. You or anyone know a way to get their attention?
cor-el said
You can consider to use the Firefox 91.13.0 ESR version if you really want an old version. Firefox 91.13.0 ESR:
From your answer I understand that you did not read and understand my post. Your reply reminds me of the sarcastic comment of a carpenter who had a hard time getting our jamming front door fixed. "Well, we can tear down the whole house and rebuild it new around the door...."
Terry said
I haven't come across the problem. The solution apparently is to type a character like a period/full stop after the first backspace, then move back before that character and resume typing. https://support.mozilla.org/questions/1388408
So, transferring your advice to a car, I always have to put it "first in reverse before shifting gears"???
Terry said
I haven't come across the problem. The solution apparently is to type a character like a period/full stop after the first backspace, then move back before that character and resume typing. https://support.mozilla.org/questions/1388408
PS Where you a developer for the Boeing 737 MCAS system? the solution sounds familiar. The latter unfortunately caused several hundred lives...
1:35 PM PDT, after clearing my browser cache it seems to work again but is still buggy. when publishing all lines are still doublespaced unlike before where only the 1st to 3 lines showed the rest hidden by a link "… Show more" Going back to edit a posted text alliance are again normal singlespaced. Only when published they appear doublespaced and all lines over the page without the aforementioned "show more" link.
Furthermore the huge blank space (1 - 2x pg down) between the actual article end (bottom) and the beginning of the comment section header still remains.
We have seen reports that Openweb has fixed this issue and that it should now work properly. You may have to reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files. * hold down the Shift key and left-click the Reload button * press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux) * press "Command + Shift + R" (Mac)