I'm using firebase authentication method signin with link,
when clicking the redirect link from email, in the first second there's firebase ui container - .firebaseui-callback-indicator-container, that appears as small empty box with loading bar, also from time to time there's weird controlbar that appears
I tried to remove it by globally catch the specific class and add to it 'display:none'
also added firebaseui-styling.global.css and imported it globally as the internet suggested
yet, nothing seem to work and it doesn't look good for ux
Adding a link with a short video to demonstrate - https://drive.google.com/file/d/1jsWhAQrojVYjylzQGUvTaTT7ifJ3tfT-/view?usp=sharing
Related
I notice that if I put a Vue website in the URL of an Instagram profile, when you click the link, as you click around the site using the Instagram inline-browser (using vue-router), the back/next buttons are disabled.
The only instance of this I can find online is here, but no other details:
https://github.com/swup/swup/issues/403
Does anyone know how this might be fixed?
If you actually click settings in browser, and then close it, all the sudden the back buttons are re-enabled, including all the previous pages you went to in tact in the history... very bizarre.
I updated our version of self asserted to 2.1.2 to address the new password reset flow. Doing this has added the social_intro to our custom log in page.
I have added the local_intro_generic to the page and it works fine, However the social_intro still show up. We are not allowing for any social login and I don't want it displayed. I can edit it... but I don't see a way to hide it either in the documents or any other search.
You can edit the html file that is getting referenced for that page. Hide the divs that you don't need after checking the class names of the divs using inspect element.
I have an elm app that incorporates logging in and fetching data from a server. Once I've logged in, I navigate to /#/pages/13 and it updates the model with page id 13. If I click around within the app, I see evidence that that page persists in the model.
When I navigate away from that page via internal links, then enter http://localhost:3000/#/pages/13 into the URL, I still see that page.
If I enter that URL while I am at that location, it seems to treat the behavior as a complete refresh, resetting the model...including my token, so it logs me out.
How can I enter the same page into the URL without elm resetting the model?
(If it matters, I am using gulp)
That behaviour seems to be by design, although I didn't find an official source for this.
The most you can do is register a beforeunload listener, which might show a prompt allowing the user to cancel the navigation.
Related: https://stackoverflow.com/a/34415095/2014893
I have facepile plugin on my webpage to show faces who are using the application.
The code snippet to show facepile is
<fb:facepile id="some_id" data-size="medium" data-width="396">
</fb:facepile>
Faces are showing normally.But when I use "Use facebook as:" option from the facebook homepage and selects any of my listed pages, facepile plugin on my webpage turns weird and shows a white box with a small thumbnail and an anchor(with text 'switch') on top of it On inspecting element with chrome's right click context menu I found it's an iframe with width being 396px and height being 1000px which displays in the middle of page hiding html form for normal login too.
If I revert to my profile using "Use facebook as:" option faces start showing normally.
Am I missing something or It's a bug?
I already checked a similar question but that is related to user being not logged.
Also I checked this bug listed
on facebook developer page but it seems to be resolved.
This is intended behaviour, although obviously the error message should be a bit better - the Facepile (and indeed, most of the Social Plugins) is designed to only work with User accounts. You can be fairly sure that 99.9% of people viewing the plugins will not be "Using Facebook as" a Page.
As Pages aren't designed to really interact with Facebook APIs (beyond the manage_pages functionality) then it is likely that these plugins won't be fixed to work for page accounts, but they'd be fixed to show a message informing anyone logged in as a Page to switch back to their user account.
You can find some related bug reports below, you should consider adding your voice to them in order to increase their priority:
https://developers.facebook.com/bugs/372904202778489
https://developers.facebook.com/bugs/313164415437524
This is the first Facebook App i've created since the Timeline changes. Everything appears to be working the same, except for adding the app to my page's Timeline "Favorites"(?) (the boxes at the top near the About section). A large majority of the traffic to this app will come from visitors seeing the app tab on our page.
I'm attempting to add it using the following URL:
http://www.facebook.com/dialog/pagetab?app_id=MYAPPID&redirect_uri=MYAPPURL
Then I select the page, and click "Add Page Tab".
This works fine - I can then swap it's position, view the app, edit settings, etc.
I set up the tab how I want it, and then log out and visit my Facebook Page directly to view the app tab as a visitor would. The app is no longer there. Log back in, everything is fine, log back out, it's gone. It appears that if you do not already Like the page, you cannot see the app. If you do like the page, you can see it. I'd like the app to be viewable by people who do not like the page as well, as the app has a fan gate of it's own.
I've disabled Sandbox mode as well so i'm not sure what's left to do.
Any help is appreciated.
You mentioned in the comments that the app is restricted to US users:
Because your app is restricted, it won't be displayed to logged-out browsers - this is expected because unless the user is logged-in, their location and age can't be determined in order to check the restrictions you've set
If you must have the app visible to logged-out users, remove the API-level restriction and use the details passed in the signed_request to show or hide the app's content
{edit} I missed the edit to your question {/edit} - it may also be that your existing signed_request processing code is failing for logged out users