You have to set up the plugin using the setup tool or whitelist your domain on facebook.com (i.e. you have to tell Facebook that the domain you are trying to run messenger on is allowed to run messenger). The setup tool asks for the domains or you can simply whitelist the domains from the facebook page settings.
Thank you @palombokevin! This worked for me on desktop. However, it does not show up when i am on ipad or on iPhone. But I see that it is showing up on your site. What did you do for it to work on iPad & iPhone? (i copied your example exactly)
I've been having problems on one of my laptops running Ubuntu Mate while viewing Facebook Marketplace using the Brave browser . A chat window covers up 1/2 of the screen so I can't view anything in Marketplace. It doesn't do it when using the Chromium browser. Any suggestions?
To try to help you, I've just installed the "Brave" web browser in my laptop computer that is running Ubuntu MATE 22.04.3 LTS ("Jammy Jellyfish") by following the instructions available at the "Installing Brave on Linux Brave" web page - - specifically by executing the following commands in a Terminal window:
I've then opened the Brave web browser, browsed to the "Facebook Marketplace" web page - - and logged in with my "Facebook" user credentials. Everything looks normal and there's no Facebook Messenger chat window opened. Even if I click the round chat icon in the lower right corner of the screen, I then get a relatively small chat window (certainly not one that covers up half of the screen as it's happening to you).
Could it be some issue related to the screen resolution in your computer? I'm using a screen resolution of 1440 x 810 (as seen in the "Displays" / "Monitor Preferences" program of Ubuntu MATE). What version of Ubuntu MATE and what screen resolution are you using? And what version of the Brave web browser are you running?
Thank you, ricmarques, for taking time to address my issue. It only happens on one laptop that is running Ubuntu, not on my other Ubuntu laptops. When I use that laptop again I'll see what version of Brave it's running. The size of the chat window is an issue but not being able to minimuze it or shut it off is what really annoys me.
I discovered the problem is due to not being able to update the Brave browser to its latest version. When using the Chromium browser it doesn't happen. When trying to update Brave I receive an error message:
"(...) When trying to update Brave I receive an error message:
N: Ignoring file 'brave-browser-release.lis' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unable to locate package brave
So, I believe that, if you rename that file from brave-browser-release.lis to brave-browser-release.list and then try again, then it should work. Please, try that and report back afterwards, in this discussion topic, to tell us if that solved your problem
I have no idea where to find the incorrect file in order to rename it. I looked in the Synaptic Package Manager and it has Brave flagged with an asterisk at the beginning of it. There were no files listed under the Repository tab in Synaptics so that was a deadend. Caja didn't list any file with that name. Thank you for trying to help.
I reinstalled Brave, restarted my computer and experienced the same Messenger chat window that can't be closed in Facebook Marketplace. There's no problem when using the Chromium browser so I guess I'll just have to use Chromium when browsing Marketplace.
So i've installed the facebook customer chat messenger plugin on my website and it works fine, but i need to align it to the left of the website and if possible also change the size of the button (it's huge).
i've tried just using CSS to align the container div but then the chat window will stay on the right side of the website... Is there some sort of attribute or option to set the thing to go to the left side instead? Surely this is something lots of other people have needed to do
For server-side rendering, if you are using Next.js, you can use its built-in server-side rendering capabilities to ensure that the chat box and its associated CSS styles are fully loaded and rendered before the page is served to the user
I marked a conversation as spam by accident (wanting to press mark unread) from Facebook desktop messenger and it got removed without ANY warning from my conversation list. Any way to revert this mess? I tried checking spam messages in mobile Facebook and see filtered requests but no luck.
Go to the app-version of messenger. Click the chat head in the left upper corner with your own image. A menu appears. Choose message requests. You come to a folder separated in two categories. Choose Spam. These are the messages marked as spam either by you or Facebook. To get it back to your inbox, the only solution I've found so far is to reply to it, but I'm trying to find other options.
I have just one thing to say if that can help you out. Please visit Facebook and go to the activity log, if you remember the date or month filter it in the search and there you may be able to do some action. I don't know exactly but I think you may find a way there.
We have Intercom installed in our web-based app but lately 20% of our users are experiencing issues with being unable to close the chat - there is no 'x' or down arrow appearing in their window. Even if it shows the down arrow, clicking it will not close the chat. The only way to get it working again is by refreshing the page.
We don't have a built-in way to add the x at the top of the Messenger window, but if you create a custom launcher it will automatically appear!
We have instructions on how to do this below
-create-a-custom-launcher
I will pass this conversation to our support engineering team to make sure there isn't something else going on for you
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
A friend -- let's call him "Bob" -- hit me up with this stumper the other day... "Why, all of a sudden, is my chat window taking up so much space on Facebook?" I asked him to open up his laptop to show me the problem, and indeed, the chat window on the Facebook page was encroaching into the content on the right hand side of the page.
Since he was using Chrome, I clicked Chrome's "Customize" (or "Menu") button -- those three little dots on the right side of the toolbar -- and checked out his "Zoom" settings. Sure enough, the zoom was set to 110%. What does that mean? It basically means that the browser was making everything it presented about 10% bigger than usual.
In a lot of cases, increasing the zoom (or "zooming in") can be helpful. It can make text and pictures bigger, which in turn helps reduce eyestrain. The drawback, however, is that the bigger text and pictures are often still tying to squeeze into the same amount of screen space. So, the browser has to make accommodations in the formatting of the webpage. And that means some elements of the page -- like floating chat windows and auxiliary content -- might be forced on top of other content or squeezed off the page entirely.
So, the fix was simple -- set the zoom back to 100%. This meant smaller text, of course, but it also meant there was plenty of room for that chat window to no longer block the view of other content on screen.
But how did this happen in the first place? Well, sometimes we can adjust the browser's zoom settings without realizing it. The most-common scenario I can think of is accidentally nudging the scroll wheel on your mouse when you happen to have the CTRL key pressed on the keyboard.
Give it a try yourself right now. Hold CTRL on your keyboard then nudge your mouse wheel a notch or two in the "up" direction -- away from you. You'll likely notice the text and images on screen getting bigger and bigger with each successive nudge. A zoom meter might also appear on screen indicating an incremental increase in the zoom. 110%... 125%... 150%... etc.
This is also a handy trick to use when reviewing documents in Microsoft Word or Adobe Reader. The zoom functionality works just the same there -- usually even better, because it typically doesn't affect formatting in those programs.
To avoid formatting problems on webpages, I generally recommend leaving the zoom level for any given page at 100%. However, don't be afraid to zoom in if you really do need it to read text better. Just don't forget to set it back when you're done.
End-to-end encryption gives people more secure chats in Messenger. These chats will not only have all of the things people know and love, like themes and custom reactions, but also a host of new features we know are important for our community. These new features will be available for use immediately, though it may take some time for Messenger chats to be updated with default end-to-end encryption.
Our new read receipt control allows you to decide if you want others to see when you have read their messages. We know people value their privacy, and this feature gives you the ability to feel less pressure to respond immediately.
Voice messaging is the fastest growing messaging format today. You can now play voice messages at 1.5x or 2x speeds, pick up listening to a voice message from where you left off, and continue listening to a voice message when you navigate away from the chat or the app.
To help personalize content, tailor and measure ads, and provide a safer experience, we use cookies. By clicking or navigating the site, you agree to allow our collection of information on and off Facebook through cookies. Learn more, including about available controls: Cookie Policy
I am testing Web Messenger with the conversation Auto Start feature enabled on my web messenger configuration. I also am testing in an environment with the Web Messenger threading timeline set to 0. The documentation states that " Under Automatically Start Conversations , select whether to allow automatic start of conversations. When this feature is turned On , conversations are initiated automatically, when the end-user expands the Messenger window."
c80f0f1006