I set out to use the ui.throbber.js plugin with 1.5.2. It doesn't officially have a 1.5.2 version, and, in fact, the version available isn't working. No throbber appears, and no errors in the Chrome console, and inspect-element shows that the javascript has run and done the surgery on the div.
I just want to start a spinner going at 'ready' and stop it when we hear back from a web service. Can someone suggest an alternative to ui.throbber.js?
I didn't find a version of ui.throbber.js that workswith 1.5.2, but I did find an alternative that will work for 1.5.2. Try nimbleLoader.
https://github.com/nimbleapps/jquery-nimble-loader
I've tested it under my 1.5.2 environment and it works and provides essentially the same result.
Related
So I've been having an issue getting my Protractor/Jasmine tests running in FireFox. I've been aware of the version issue from FireFox that doesn't support selenium angular/bootstrap etc etc and that has been my issue to date.
I was informed to try geckodriver but really can't find any good resources on how to set it up using protractor and jasmine. Or even which driver is the appropriate one to use.
Recently I've tried the following to get FF back up and running (all resulted with no luck):
Downgraded FireFox to as low as 33.x.x while keeping
Protractor/Jasmine at current versions (4.0.5 and 2.51 respectively).
Downgraded Protractor to as low as 3.0.0 while keeping FF at current version (47.0.1)
Downgraded both Protractor and FF to the lowest above versions.
Used Latest Version of FF 47.0.1 with lesser versions of Protractor.
Used Latest Version of FF 47.0.1 with latest version of Protractor 4.0.5
Used directConnect: true and directConnet: false
So I guess now I have one of two questions:
1. Could somebody post a protractor config snippet using the geckodriver / or direct me to a walk-through of this.
2. Inform me of a work around or a working solution (versions of both webdrivers/protractor/jasmine, etc).
If you need to see errors or my config file or anything at all please just simply comment and I'll be happy to revise.
There was a period of time around Firefox v46 and Selenium v2.5x where things were incompatible due to changes to the firefox web-driver. The issues were quickly addressed by the community.
The issue with Protractor lies with the webdriver-manager being a bit out of date with the updates. As per discussions on github, they are aware of this, and a fix is coming.
The workaround in the meantime is to manually update the outdated pieces.
Here's how you'd do it, run
webdriver-manager update
This will give you the paths to all the components the webdriver-manager handles for you.
Navigate to the selenium-server-standalone.jar file (protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar in my case) and replace this with the latest selenium standalone jar (anything v3+ should be good). Make sure to retain the exact filename as the previous jar file. (link: http://www.seleniumhq.org/download/)
Repeat the process to get the latest Gecko web-driver. Uncompress and replace the current version. (link: https://github.com/mozilla/geckodriver/releases)
Now run your tests through protractor and you should be good with the latest version of Firefox.
Good luck and happy testing :)
I have firefox 31 in my testing machine and I am using Robot framework to test functionality.
Before I was facing the problem like if I update firefox then my test case fails and then I did some research on it. Finally I found that there is lag between the time release of Firefox version and Selenium updates accordingly.
So now I am confused that to make our testing environment stable with new updates, how to proceed?
What could be the procedure for this Patch of firefox and Selenium library ?
Thank you.
If I understand correctly, updating FireFox causes an issue as sometimes there can be breaking changes, which are not addressed until a later date by Selenium?
If this is the case you have a few options which I imagine you're already aware of:
Don't update until the Selenium update is released, until then, do not try and support something that could break.
Update where you can, if a breaking change has been introduced, rollback and state you don't support that browser version. With this method there's obviously potential for waste.
Update and make changes to the tests in order to get them working for the latest version. You can revert once the Selenium updates are out that address any breaking change.
Personally I would opt for the first option, given it is by far the simplest. However, this may not be an option for you.
http://coldfire.riaforge.org/
I can't get the current version (1.9.207.249) to work in with Firefox 14.0.1 with Firebug 1.10.2.
I assume it is broken because the plugin has not been updated for the release of Firebug 1.10.
Has anyone got it working with these settings?
A new version of ColdFire was released that should work with Firefox 15/Firebug 1.10.
https://github.com/nmische/ColdFire/downloads
Based on this I will assume it's still alive. Perhaps try the Chrome version?
http://www.raymondcamden.com/index.cfm/2012/8/24/First-release-of-ColdFire-for-Chrome
I am requiring the date library and I would expect the methods from this library to appear in the code completion list (and hence get the documentation inline). However nothing appears. Why so?
What RubyMine and Ruby version are you using? Please try 4.5 Release Candidate, everything works fine for me in that version
I have installed in TYPO3 the extension ods_pm_ajax for ajax submit, but for some reason this doesnt seem to work. I get an error like in line 5 of ods_pm_ajax.js, because $.style is not defined, which makes me think that it doesnt use prototype but I dont understand why! I turned off jQuery in my site because I was afraid of compatibility problems and still nothing.
Anyone has an idea of why this can be?
What version of ext powermail are you using?
I tried with 1.6.4 and got very similar error to yours. And then downgraded to 1.5.7 and it started to work!
Looks like the extension odd_pm_ajax requires 1.5.x. I think with version 1.6.x powermail started to use jQuery for javascript framework.
Changelog for 1.6.0 version of powermail copied from TER:
1.6.0: jQuery validation, extJS BE Module, Scheduler, HTML templates modified!, see http://forge.typo3.org/versions/show/678 and manual
So just use version 1.5.x and ods_pm_ajax should work.
Or try to achieve the same functionality with 1.6 and jQuery.
Cheers