I have a page with a Google Maps component, and I am using navigator.geolocation.getCurrentPosition() on initiating the map so that I can show "local" items.
Everything works great, other than the behavior of the location prompt - In the past I thought I had seen where you could choose to allow FireFox to remember this setting, but that has either been removed from FireFox, or there is some flag/setting that I'm not using that would enable this... anyone have any insight?
See this page for a screencap of the 'remember' checkbox:
http://diveintohtml5.info/geolocation.html
Thanks,
Paul
EDIT:
Ok, looks like I am only seeing this issue in FireFox 4, in that it doesn't seem to give me the option to remember the site in the prompt, which means it prompts each and every time. FireFox 3.5 works as expected. Is this expected behavior? I can manually set it to never ask by going into Page Info for the page, but the typical user is not going to know how to do this.
Well, it appears that version 4.0.1 of FF doesn't have the 'remember permission' checkbox... the user will get prompted each and every time they hit the page until they perform the following steps:
Right-Click->'View Page Info'->'Permissions' Tab->'Share Location' and then un-check 'Always ask' set the radio button to 'allow'.
Seems like most people would never know to look there for this setting though, hopefully they re-introduce the dialog 'remember' checkbox.
If you did already gave permission, Firefox will not ask again. You may undo it according http://www.mozilla.com/en/firefox/geolocation/
Related
I created a login sequence and my selectors for the input email, password, click login and element exists are valid. But only when I have the Internet Explorer page open on the website I'm working with.
I did that sequence again, and I ran it, initially it worked but when I ran the hole project it broke again, I tried "repair" and "indicate", I tried to eliminate the title but nothing is working.
As far as I can see, you are using selector attribute:
"title=ACME System 1 - Dashboard"
Try using a wildcard: title='ACME System 1*', so it can work when you leave the dashboard.
This worked for me when I took those UiPath Academy courses.
In order to automate tasks within a browser with UiPath, the browser must be open. There is an activity called Open Browser that's included in the default activities for every project. You need to add this activity to the beginning of your sequence and pass in the appropriate parameters, (ie. URL, browser type) you can then pass the outputted browser variable to an attach browser sequence and execute your browser automation acivities within that.
Browser activity sceenshot
In addition, the selector that you have shared does not look like a stable selector. There may be other 'H1' elements on the screen that will cause your automation to fail. I would use the UI explorer to help you build a better, more stable selector.
Did you initially use IE to indicate screen elements and then changed the BrowserType property to use a different browser? Please share the sequence to suggest you a fix for your issue.
I would also suggest you to modify the selector to 'title='ACME System *'.
In order for selector to work the application needs to be open and the desired element needs to be available. So when you close the browser the selector disappears.
You may consider swithching to 'Modern Design Experience' and use 'Use Application/Browser' scope to make this more intuitive, and it will also automatically open the browser for you if it is closed.
Long story short:
I tried to create/edit GitHub Gists with
Firefox 67.0 on Windows 10
Firefox 67.0 on Linux Fedora
Add-ons: NoScript, Ghostery, LastPass
Tried with NoScript and Ghostery disabled and also with NoScript in "all shields down" mode and also with Firefox in "safe mode".
Problems:
Creation of a Gist is arbitrary. More often than not, the two buttons "create public gist" and "create secret gist" just stay disabled and the editor widget is "dead".
Occasionally, creation works, the editor widget goes lives and displays line numbers and the editor buttons become active. But it happens annoyingly rarely.
Editing a Gist is arbitrary. Again, it sometimes works but currently I just get blank editor widgets that have no cursor.
Anyone else who has these problems? It may be a temporary hiccup, or maybe there is some JavaScript that Firefox doesn't like. However, a web search brings up nothing - I can't believe I am the only one stuck with this this.
My earlier testing fails completely. I was sure I had tested in safe mode with no change in result.
However I retested with the latest Firefox update (FF 67 on Linux) and found out that it is the LastPass plugin which is the root of the problem. I would not have suspected that.
Disable that plugin, leaving all the others active and Gist creation and Gist editing work.
Enable that plugin and Gist creation and Gist editing work once after a Firefox restart. But after that, you get the unresponsive text entry widget.
Similarly, running Firefox in safe mode with all plugins disabled also fixes the "problem".
And of course, if you do this using Konqueror instead of Firefox, creation/editing work too.
In Oracle Identity Manager I have a problem where when I activate a sandbox and I want to change something on the create user tab on the User Interface I click on a field and nothing happens. Does anyone have any ideas on how to fix this? I tried rolling back old sandboxes and putting extra logs but there is nothing that can help me.
In all other tabs it works fine. For example in modify user it works. Only in this tab it doesn't work.
I use Firefox browser. I tried through Microsoft Edge and Google Chrome and it works fine there.
FF works fine for me. Some things to further troubleshoot your issue.
What are the specific steps you are taking to replicate the issue?]
Have you tried different versions of FF?
Steps that i took.(PS3)
1. Activate sandbox
2. Click manage
3. Click Users
4. Click create
5. Click Customize
6. Click structure(errored out as there are required fields, put random values in lname, org and user type)
7. Clicked structure again, this time it worked and i have normal control over the fields i would like to customize.
It worked until today, no code got changed
So if I do something like
page.find('#edit-user').native.send_keys(:tab, :tab) it's not working (it's highlighting the element #edit-user but not moving forward) specifically for the tab key, it's working correctly for :space or :enter.
It was working previously, it's a small possibility that it's related to some settings change for the Chrome browser but not sure exactly how and why
We are having this problem in Chrome as well, and it all started with Chrome update 44.
I tried using "\t", :tab, :return, :enter, and :escape to remove focus from a text input (symbols found here), but none of them are working in the most recent version of Chrome.
I know you mentioned you are not looking for solutions other than tab, but short of rolling back your browser version and disabling updates, or waiting for the possibility of a fix from Google itself, you will have to change the scripts being executed.
We found that this has worked well so far:
driver.execute_script("document.activeElement.blur()")
If the desired behavior in your case is to shift focus two fields forward, then you might consider another Javascript solution that looks something like what is discussed in this thread:
simulate the tab key function in javascript
Of course, this probably isn't the best long term solution, as even some very quick Googling shows that sending a tab key to switch focus has been recommended tons of times to people using WebDriver. Because of this, I'm keeping my fingers crossed there will be another Chrome update to revert the behavior.
How do I know which part of JavaScript that is executed when some event is occurred in Mozilla Firefox?
This is a very broad question but I'll take a shot. I was a bit curious about the now native debugger in Firefox so I looked into this for you. Firebug is still a nice tool but you don't need it for debugging if you're running Firefox 19 or later. Let me also suggest trying Chrome's DevTools, they are my personal favorite.
To use the native debugger in Firefox, there's two options you will need to configure. Go to about:config (paste that in the address bar). Proceed past the warning. Update the following settings to be true (search is your friend):
devtools.chrome.enabled: true
devtools.debugger.remote-enabled: true
You need to do that so you can set breakpoints in the code. Now load the debugger, the shortcut is Ctrl+Shift+S.
At this point you need to have some idea where to set your breakpoints. If you wrote the JavaScript, you shouldn't have much trouble. If you're inspecting 3rd party code, you might need to browse the source code to get an idea where to begin.
With the debugger loaded, select a source file in the dropdown. It could be a JavaScript file, or any other resource that has JavaScript. You should open whichever file you're interested in inspecting.
To add a breakpoint, click to the left of the line number. You can also right-click on a given line and select "Add breakpoint." If you are debugging something that happens on page load, refresh the page. If it's an event handler, interact with the page to fire the event.
Those are the basics you'll need to get started with debugging in Firefox. Here are some resources you might need to go further.
MDN article: Debugging JavaScript
YouTube video using FireBug: Firebug DebuggingIntro
Chrome DevTools: Breakpoints in Chrome
I hope that helps!