Facebook Issue

[WilsonFlyer]

Extension 2.1.0

Every time I respond to a comment on FB and type "Shift + S" with a word in it (capitalize an s), my screen goes blank with just the facebook banner across the top and the ads on the side, but all the content in the center is lost. When I reload, FB warns me that my post will be lost. It's already lost! All I typed is lost. With no way to recover that I can find. I can duplicate the problem every time and it does not happen if I disable the extension and refresh the page.

Below is what happens when I type Shift + s in a comment. Every time. It is duplicable across all Chrome browsers on all of my machines. In the interest of full disclosure, I am logged in to Google and all of my settings follow me.

Could someone please see if they can replicate my problem?

Thanks!

[rakka]

I am not able to reproduce the issue at my end, btw what is Shift+S for?

[WilsonFlyer]

How could you possibly know that you couldn't duplicate it if you didn't understand what I said? Nice work.

If you don't know what shift+s means and are in technical support, forget it. I'm on the wrong forum with the wrong developer.

[exile360]

3 hours ago, rakka said:

I am not able to reproduce the issue at my end, btw what is Shift+S for?

The OP is simply referring to typing a capital 'S' in the post editor/text field on Facebook; it isn't a special command/shortcut or anything like that (though if there is some sort of shortcut/command in Chrome using those keys, that might at least partially explain the observed issue, however I searched and could find no reference to such a command and usually browsers use CTRL+<key> for their commands or ALT+<key> similar to most Windows applications).

Edited October 15, 2019 by exile360

[exile360]

By the way, I did find this page documenting all of the Chrome keyboard shortcuts as well as this page documenting various browser shortcuts for Facebook, however I found no reference to any SHIFT+S command (CTRL+S would be to save a file/document in most applications, however that obviously is not the key combination in question).

[WilsonFlyer]

I'm just trying to capitalize an "s" folks. No need to make it rocket science and no need to read between the lines. I can't put an "S" in a comment. :)

[exile360]

Yes, I knew what you were saying, however if that particular key command happened to be used as a keyboard shortcut for your browser or for Facebook, that might have explained why this issue was occurring so I was just being thorough.  The fact that this happens whenever you enter that particular key combination is very odd so clearly there is something more going on here, and I'm just trying to figure out what that could be since obviously that particular combination shouldn't have anything to do with the browser extension and certainly should not be causing the behavior you describe, and since no other users have ever reported it, I'm just trying to find out why it might be happening on your particular systems.

Since you mentioned that you keep Chrome synchronized across devices, the first place I would look would be at your extensions.  If any of those happens to use that particular key command then that is likely your culprit.

Edited October 15, 2019 by exile360

[WilsonFlyer]

I'm starting to worry about sounding condescending and I don't mean to. I've been in the industry since its inception. Literally.

I've turned all of my other extensions off with nothing active aside from the Malwarebytes extension. It does it every time unless I turn it on. Again, not meaning to sound condescending, but you do understand that no extension or browser activity can intercept (obviously the Malwarebytes one is, however.) Shift+a character or symbol? Those are typing keystrokes by definition. I'm just trying to figure out why Malwarebytes apparently is trapping this sequence and why the result is what I posted above in FB.

Whatever happens is particularly odd because when you attempt to leave a page you have commented on and not submitted, FB always pops a dialog saying your post will be lost, however; when I hit Shift+s during a comment, the blank above just happens. No dialog, unless I attempt to refresh the page or go <back.> Either of those actions produces the warning dialog. 

Would you be so kind as to try it and see if you experience the same result? That would help. It certainly could just be unique to my configurations. A first step, as I asked in the OP, is to see if it is a duplicable result for at least one other person. 

It's been happening since the beta. I just never got frustrated enough to tie it all together until today when I had to make a post with the name Susan in it and couldn't even use her name in the post. It probably didn't happen until a few days after the installation of the beta version because I probably don't use capital S's that much so I just never tied the two together. I just thought it was an anomaly with FB to begin with. FB has its own share of quirks in browsers also, and there's no use in reporting anything to them because they are about as supportive as <insert name of your least favorite company for customer support here> is. At the end of the day, it ended up not being them anyway.

[WilsonFlyer]

That should say "unless I turn it OFF." You can't even edit posts here? Wow.

[exile360]

I don't use Facebook or Chrome (though I do use SRWare Iron, which is also based on Chromium, just with the Google parts cut out) so I can't replicate it, however the Support and QA guys should have no trouble trying to reproduce it.  You are correct that Malwarebytes shouldn't be intercepting your keystrokes (none of them in fact; it doesn't even support any keyboard shortcuts).  We'll have to wait to hear back from a member of the staff, but in the meantime I'll also document this for the Product team to submit it for analysis.  They can get the Devs to investigate it from their end assuming they can replicate it.  In the meantime, if you would please do the following so that they can take a closer look at your installation and configuration:

1. Download and run the Malwarebytes Support Tool
2. Accept the EULA and click Advanced tab on the left (not Start Repair)
3. Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply
   

Thanks

[exile360]

I just thought of something else.  Have you tried typing your text into a separate editor like notepad then pasting the text into the Facebook editor?  If so, does the same issue occur when the text contains a capital 'S'?

[WilsonFlyer]

I guess I should have posted that. I tried that and no. Copy paste from another word processor does not duplicate the problem. It is the stroke happening in the active comment box that generates the problem. I'm not sure there aren't others that would do it also, but I am sure of that particular one.

Thanks for your help.

[exile360]

Thanks.  Does the same happen if you use the On-Screen Keyboard built into Windows?

[WilsonFlyer]

Good question. Yes. The behavior seems to be similar from what I can tell.