My Firebug and Firepath were working fine, but they just started acting strange. When I click on objects on webpage, and do Inspect Element, it just does nothing. I didn't update or do anything on firefox. Anyone else having similar issues?
Well I tried the next release 1.8.1b1 and it still failed. I reinstalled 1.7.3 and its working again. Here is the link:
Addon Firbug 1.7.3 Download
and the versions page:
https://addons.mozilla.org/en-US/firefox/addon/firebug/versions/
It's ok now,firepath 0.9.7 is compatable with firebug 1.8
Related
Mozilla Labs has an extention called "Recall monkey", it stop working with new versions of Firefox, my question is what is the last Firefox version that does support it. i searched it but found nothing , Any help is appreciated.
these links may help:
Mozilla labs:
http://mozillalabs.com/prospector/2011/06/20/recallmonkey-finds-what-you-forget/
Addons link:
https://addons.mozilla.org/en-US/firefox/addon/prospector-recall-monkey/
what does this addon do:
https://superuser.com/questions/296501/is-there-a-way-to-search-the-text-of-my-browsing-history-in-firefox
According to the plugin website it should be supported from version 12 up to 21.*
Searching browsing history is super cool. I think they are bring it back with this Test Pilot addon - Activity Stream - https://testpilot.firefox.com/experiments/activity-stream
Until today GM_setValue was working perfect. I have actual version of GreaseMonkey and FF. And today it stopped working. In current version and latest version i have "GM_setValue is undefined". Also GM_setValue stopped working. I didn't change anything in script, nor in browser (maybe it updated in background?) How to fix it?
Did you set the #grant option in the header to allow GM methods?
I'm getting a TypeError: elem.dispatchEvent is not a function using select2 in jquery using the wrapbootsrap pixel-admin theme.
It can be reproduced in firebug on the demo site via http://radiant-ocean-4606.herokuapp.com/forms-advanced.html
Firefox Version: 29.0.1
Firebug Version: 1.12.8
It's a similar error message to this question:
"element.dispatchEvent is not a function" js error caught in firebug of FF3.0
But the answer there doesn't help me as my site is all jquery (well as far as I know - I did somewhat accept the theme bundle as it came for the time being until I have time to really rip it apart and modify it in detail).
This was caused by changes to the browser, the solution was to stop using firebug. The features firebug offered are ubiquitous now!
I am using ruby/cucumber/watir-webdriver and the page-objects gem to run my tests. My tests are usually run in firefox but decided to give chrome a try. While the click works in firefox it does not in chrome. Here is the sample html code:
<form id='test-form' method='post' class='validate-inline'>
...
<div class='margin-top'>
<input class='btn' data-disable-with='wait...' type='submit' value='Submit Form'></input>
</div>
</form
In my class page I have the button declared as the following:
button(:submit_form_btn, :value => 'Submit Form')
And call it this way:
submit_form_btn_element.when_present.click
I do see the button text change to 'wait...' for a few seconds then returns to 'Submit Form' but does not seem to submit the form. As mentioned before it works with firefox and when clicked manually. Just seems to be an issue in Chrome. Any ideas how to get around it?
I tried clicking the div, and tried clicking the button twice but same issue.
As always your help is appreciated. Thanks.
I know this question is little old now, but I thought I'd post in case this helps anyone.
Most of the times I've run into similar issues, it was caused by an update to Chrome that caused issues with the version of the watir-webdriver gem (or one of it's dependencies) or with the version of chromedriver that I was using. I've had success in the past by updating my gems and chromedriver and the other times I've had to roll back the browser version to the previous release.
It's not ideal to be testing on an older version of chrome but it worked fine as a stop gap until the issue was fixed.
If you do go for the previous version of chrome approach, make sure to log a bug ticket if there isn't already one there.
I'm trying to buy something at Paypal-Sandbox with Selenium RC (Java), but it doesn't work.
I tried it with Selenium IDE (Firefox AddOn) and it did work. I changed the viewing and copied the JUnit 4 Code and it still doesn't work.
The problem is the part with the radio-button "payment_type_paypal". Somehow it doesnt work in RC (the radio-button is not checked). Do someone have similiar experiences and/or resolved the issue?
After loging in to developer.paypal.com and entering the homepage...
//linking homepage
selenium.click("legalTerms");
selenium.click("pay");
selenium.waitForPageToLoad("30000");
//leaving homepage and switching to paypal
selenium.click("payment_type_paypal"); // <===== point of error
selenium.type("login_email",username);
selenium.type("login_password",pw);
Thx :)
its me againg, Krzys. I know now the Problem. Its an issue with focussing the correct frame. I couldn't get it work with Selenium RC.
You can easily fix the issue in Selenium WebDriver with the command, before my "point of error":
driver.switchTo().defaultContent();
its me again. If you encounter problems with the Sandbox System of Paypal, you can overcome the "submit"-button issues using xpath.
driver.findElement(By.xpath("//div[#id='nav-menu']/form/ul/li/ul/li[6]/input")
Greetz
Krzys