Selenium webdriver using switch_to_windows() to latest popup window

driver.switch_to_window(driver.window_handles[-1])
title=driver.title

You can do it simply use the code above. driver.window_handles[-1] would get the lastest window.

reference : http://stackoverflow.com/questions/13113954/selenium-webdriver-using-switch-to-windows-and-printing-the-title-doesnt-prin

Set value of input instead of sendKeys() - selenium webdriver

inputField = driver.findElement(webdriver.By.id('gbqfq'));
driver.executeScript("arguments[0].setAttribute('value', '" + longstring +"')", inputField);

reference : http://stackoverflow.com/questions/25583641/set-value-of-input-instead-of-sendkeys-selenium-webdriver-nodejs

How to know current frame with selenium-webdriver

I have a code like this.

require 'selenium-webdriver'
driver = Selenium::WebDriver.for :firefox
f = driver.find_element :xpath, "html/frameset//frame[@name='header']"
driver.switch_to.frame f

After switching frame, is there a way to access attributes of current frame? In other words, how can I get value of attribute name of frame tag after switching?

I want to be sure I'm handling correct frame before to do something.

Related questions:
is their any way where i can view my HTML code into frame (selenium webdriver and Java)
How to identify and switch to the frame in selenium webdriver when frame does not have id and title

2 answers

By ArtOfWarfare

This was officially requested and rejected in 2012, here:

https://code.google.com/p/selenium/issues/detail?id=4305

The answerer asserts that this was rejected because you can use this (Java) code to accomplish the same thing:

WebElement el = (WebElement) ((JavascriptExecutor) driver).executeScript("return window.frameElement");

Personally, this strikes me as an asinine answer - the entire JavascriptExecutor portion of Selenium just seems like an ugly hack to allow end users to do things that the developers didn't anticipate would need to be done. Except the developers were clearly told this needed to be done, and they ignored it.

Anyways, I'm using Python which allows additional methods to be dynamically added to existing classes (even those which you don't have access to) so I just used the following to give WebDriver a currentFrame method:

from selenium.webdriver.remote.webdriver import WebDriver

def currentFrame(self):
    return str(self.execute_script("""
        var frame = window.frameElement;
        if (!frame) {
            return 'root of window named ' + document.title;
        }
        var ret   = '<' + frame.tagName;
        if (frame.name) {
            ret += ' name=' + frame.name;
        }
        if (frame.id) {
            ret += ' id=' + frame.id;
        }
        return ret + '>';
        """))

WebDriver.currentFrame = currentFrame

(I'm just using this for debug/logging purposes - I don't actually need the WebElement so I'm just returning a string. I don't know Ruby, but I'm sure you can adopt either my Python code or the Java code I copied from the other website to make it work in Ruby.)

reference : http://www.scriptscoop2.com/t/6510b44786dc/ruby-how-to-know-current-frame-with-selenium-webdriver.html

Because after all these years, IE still sucks

So, what is it?

Bless provides an elegant solution to a lesser-known bug in Internet Explorer which causes CSS to be completely ignored. It runs server-side and on your local machine with Node.js

Say what?

IE versions 6, 7, 8 & 9 all have a limit on the number of selectors allowed in a single CSS file. Once the limit is reached, IE silently fails and just ignores any further CSS in the file leaving parts of your site totally unstyled.

File size, number of lines or amount of whitespace are irrelevant. Minifying CSS will not help you here.

I've never come across this before...

Chances are, so far you've worked on smaller scale sites and/or separated out CSS across multiple files. Once a project reaches a certain size however, there's no going back.

If you're using a CSS compiler such as Less, Sass or Stylus it's likely that you're exporting everything to a single CSS file to reduce http hits. If your project is a substantial one or you're using a base template such as HTML5 boilerplate, you're a prime candidate to have come across this issue or will encounter it soon.

Check out this page in IE and you'll notice a visible difference. There are no special methods being used to target Internet Explorer - IE is simply ignoring the CSS which makes this page's color scheme blue.

So what's the solution?

Keep the number of selectors in a single file below the limit by splitting your CSS over multiple stylesheets.

Totally lame to manage manually, and unless you keep count of the number of selectors per file you'll probably end up taking additional http hits because you separated styling out into several files for organization or 'just in case'.

Help!

Relax. Download bless and you're all set. Or alternatively:

$ npm install bless -g

Usage

Pass in a CSS file and your stylesheet will be split into the minimum number of files necessary to keep you out of trouble. If you're already below the limit, no action is taken.

$ blessc style.css

There's no need to change your markup to include any additional files. @import directives are added to the file you originally provided. Pass in the -x option to 'minify' those statements.

$ blessc style.css -x

If you removed some styling since you last ran bless, you may now require fewer CSS files. Any previously generated files which are no longer needed are removed by default. Disable by using the --no-cleanup option.

$ blessc style.css --no-cleanup

It's even possible to read from stdin for your input, which means you can pass the output from your favorite CSS compiler straight to bless by using '-' as your source.

$ lessc source.less | blessc - output.css

If you're not using one of the aforementioned CSS pre-processors but are going old school with straight up CSS, you probably don't want to mess with your source file. To preserve your original file, you can output to a new set of files by passing in a destination filename.

$ blessc source.css output.css

Check which version you're running.

$ blessc -v

Turn off the cache buster.

$ blessc source.css output.css --no-cache-buster

Is this going to slow down my workflow?

The example.css file below contains 12,286 selectors. Bless splits it into 4 files in 0.19 seconds.

Demo

Download this example css file and try it out.

Why the weird name?

It was born out of using Less, and seems an appropriate verb. You 'Fedex' parcels, 'Google' yourself and 'Bless' CSS files.

This would be awesome as part of...

If you want to integrate with Bless, please contact me.

reference : http://blesscss.com