So in devtools of google I managed to hit shift ctrl + m i believe. Now facebook won't stop going into mobile. How do i get it into normal view? - devtools

>.<
I disabled this
But it still keeps being in m.facebook.com

Related

Facebook 'Continue' button misplaced in Chrome Extension oauth popup

I'm using chrome.identity.launchWebAuthFlow to start the login flow and when the user oauths with Facebook, the bottom 'Continue' button is partially out of the view. When the user has to enter an email and password for the first time, it's fine, but when Facebook asks only for the password the next time, the issue occurs. Also on the 'Forgotten you password?' page.
Since chrome.identity.launchWebAuthFlow doesn't allow to set size, and resizing the window manually moves the button, but at the same misplaced position, I see it as a clear sign that it's Facebook's code or the chrome.identity.launchWebAuthFlow's window's quirk.
When opening up the same auth url in a real browser window, the button is placed at the right place.
Anyone else came across this issue? Is there any good workaround?

How to bring interacted IE browser to the front?

Im using RPA blueprism. Ive 2 interacting browser which is passing data between each other but i cant bring the currently interacted browser to the front. That means the process is running on the back of the first browser. Is there any global action that i can use? Ive managed to get the PID of each browser and ive tried using Focus action on html element but no luck. Do help and TQVM in advanced.
Try spying the entire browser as an element and in navigate stage use activate application. it brings the browser to the front.

elinks http autentication

I'm trying to use linux elinks text browser to go to a website. This site requires http authentication. If I press escape it and hide the login prompt once and then If I try to go the particular website again it doesn't show the login prompt again. I try "flush all caches" But it doesn't work until I close my terminal and get a new one. Is there any other way to get over with this?
This should be a simple question. But I googled and couldn't find a answer.
I just tried this with links version 2.2 on Fedora 17. I went to a website that requires basic authentication, got the popup password dialog, hit escape, saw the error msg. I then hit Ctrl-R to reload the page and was presented with the username and password prompt again. So I hit 'g' and entered 'google.com', went to google. Then hit 'g' and went back to my password protected site, and I'm asked for the username and password again. So I can't reproduce this issue.

Browser navigation, back button issue

I want to know how you guys deal with back button issues in your web applications.
I can not forbid users to click back button on their browser, but when they hit it, the page code doesn't run. So writing in page_load() makes no sense.
I have searched online and found this link: Disabling Back button on the browser. It does not work for me. Any idea?
There is no way to disable the back button. You can try to open your page/form in a new window so there would be nothing to navigate back to
Normally, If I have a critical or lengthy form, I tend to maintain a dirty-flag and if the user starts entering something, the dirty-flag gets set and on save or submit it gets reset. You can use unload/beforeunload javascript event to see if the dirty-flag is set and ask for confirmation.

UIWebview Facebook Connect

Inside a UIWebView the user can click on FB connect button the page displays and when I hit login the UIWebView turns blank and stops there.
On a regular browser after the login is hit, it looks like it goes on fb and redirects back to the webite. I'm not sure what to change on the UIWebView so that it handles it like Safari does
edit:So when I try it on the simulator's safari, hitting the FB Connect button, it opens a new page that shows the login form and then it closes and goes back to the first page after hitting login. SO i guess the question: Is there a way for UIwebView to handle this?
The real problem was using the regular facebook login as opposed to the m.facebook.com login.
Which avoids creating a pop up.

Resources