This is from the Messenger app within Facebook so the symbols are white with a blue dot because of the message background color. In Facebook itself, in "status" posts and comments, the symbols appear in similar fashion as black rectangles with white dots. Looking at it refreshes my impression that these errors are related to the issue with the backspace key. I think the symbols appear in spots where I've used the backspace key for corrections/edits.
OK, thanks. Just to be clear, these things appear in Facebook/Messenger *only* when I enter text via TenFourFox on my G5. The fact that they're visible only in Windows is a further oddity. I didn't even know about the problem until a friend with a Windows laptop asked me what "those little black boxes" were that kept appearing in my Facebook posts. Safari doesn't do this, but Safari isn't a good solution for reasons I'm sure I don't need to go into here. :) Oh well, not a big thing. If it weren't for all the other tasks and sites that TenFourFox can handle where other browsers stumble and choke—and I'm pretty sure I've tried them all, repeatedly—my faithful and beloved G5 would probably have been recycled long ago.
I hadn't considered that, though the positions they appear in the screenshot don't really look like where a deletion would typically occur. Did you enter those with the delete key at those points, Kathi?
Can't reproduce it.
Picture 1 is what it looks like in TenFourFox (posted from TFF with several corrections using the Delete key; issue 8336 is still present).
Picture 2 is what it looks like in Firefox 45.9 on Win XP.
Cameron: I'm 99% sure one of the two keys that delete triggers these glyphs to appear in text that I have edited. I would wager that it's the backward delete because (1) that's the one that acts up on Facebook (as someone mentioned in one of the other threads, the back-delete tends to delete only one character and then not respond to being repeatedly struck), (2) it's the key I am most in the habit of using for deletions when editing/correcting something I've typed. For example, in my screenshot it looks like I was trying to delete excess "spacebar" spaces. I often end up with extra spaces when I edit posts before sending, and I have the impression that is the most common circumstance for the glyphs to appear. I remember one recent instance when I composed a post outside the browser and pasted it into TFF, and I still got one black box—at the very beginning of the post, where I recall trying to delete a space.
Chris: I have never worked with Virtual PC. Is it possible it doesn't replicate Windows 100% in this context? BTW/FWIW, my Dell XPS 8700 is running Windows 7 (because I'm too stubborn to pay for an upgrade).
Here's a test I did just now. A little surprised there are no stray glyphs in the third sentence. Sometimes when editing I highlight/delete rather than deleting character by character with backspace or forward delete. I think I did do that in the second sentence, where there's a string of five of them. I wonder if the highlight/delete action is the true culprit here…
I just questioned my Facebook friend who originally pointed them out to me, and when she's on her Windows laptop, she said, she is usually browsing with Chrome, too. Neither of us can see the glyphs in iOS.
Wow. Thanks so much for looking into this further. Very interesting and informative for me. I would never have thought to look in the inspector. Since you took the trouble to show me an image of the evidence, I inspected the test post I made this morning and sure enough the extraneous characters show up as they do in your test (see snip below). At least I have a better idea how to prevent the problem even if it can't be fixed. Hat tip to Gecko as well :D
After struggling with this all day the issue looks like, at some point with repeated delete key events, Facebook stops treating them as backspaces and starts inserting the actual backspace character code.
Although this gives me a little more understanding into the Facebook delete key problem, unfortunately I'm hitting the same wall I hit with looking at this before, namely that Facebook uses many non-standard methods for its user interface and is heavily dependent on a large battery of minified scripts which are extremely hard to debug (besides the fact I really, really despise Facebook personally). My suspicion is that our custom widget code is not filling in a field in the DOM keyboard event that it's expecting, but several shots in the dark didn't seem to make a difference.
For now all I can suggest is using either the forward delete, which seems to work just fine for reasons I am unable to determine, or cutting and pasting. If you find a less complex site that does the same thing, I can take a look at that.
Thank you Cameron. I know Facebook is awful in many ways of which you're keenly aware, so I hesitated to even bring this up. I appreciate your looking into it and by doing so, you and Chris have given me a much better handle on the issue. I should be able to avoid triggering the glyphs now by taking care not to use the backspace delete when cleaning up my text entry errors, and if I forget occasionally, well, my Chrome-o-phile friends will just have to deal with it. Without your help I probably would never have figured out that Chrome is the only (major) browser that shows the glyphs.
Even more, I appreciate the huge gift of TenFourFox that has kept my Power Mac G5 in daily use for going on 12 years now, as a classic and a beast the likes of which I won't own again. I'm writing this on the 2012 Mac Mini that sits next to it, but that's only because the G5 and TenFourFox are busy filling a shopping cart :)