Closed Lagistos closed 6 years ago
I have the same problem except it does not show in chome either.
Thank you about your answer. but the problem is still exists
In my case I needed to initialize the module first. It showed up once I did that. It wasn't clear what functions required initialization and it failed silently. On Sat, 27 May 2017 at 3:38 AM Lagistos notifications@github.com wrote:
Thank you about your answer. but The problem is still exists
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/zyra/ngx-facebook/issues/79#issuecomment-304435278, or mute the thread https://github.com/notifications/unsubscribe-auth/AQaDGOG64NVAra4sGrO_ZdTmne9VVVkPks5r99LxgaJpZM4NjiOV .
I did the initialization function again inside the constructor and yet not working on chrome, all the components working well except the comments component (and it's working well on firefox and edge) even after i updated my chrome it didn't work.
Ok I'll look into it.
The example project for this repo works fine on Chrome and it shows every single component correctly.
It's worth checking if you have any browser extensions blocking the comments component.
i dont have any extention on my chrome, i hope that it's a problem in my browser, thanks a lot.
Does the example project work fine for you?
actually no, and i just checked it on other websites with facebbok comments and it doesnt work there also, so probably the problem is in my browser, thanks a lot
It's not showing on opera too. The input href
is removed when building the project
This what I write in HTML <fb-comments [href]="post.link"></fb-comments>
And this from console
Reopen the issue if you still have this problem.
Hello,
I still get the issue, I am using ngx-facebook plugin (or ng2-facebook-sdk) and it perfectly works on Firefox but not loading my
Any idea on a workaround ?
Thanks a lot
I added a comments area and it's look ok on the firefox and edge but it's not visible in chrome. does somebody is familiar with this problem? is there a way to fix that?