<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr - noah</title>
<link>http://snipplr.com/users/noah/tags/client</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Thu, 20 Jun 2013 02:47:17 GMT</pubDate>
<item>
<title>(Other) How to configure the output format of the W3 CSS Validator</title>
<link>http://snipplr.com/view/19817/how-to-configure-the-output-format-of-the-w3-css-validator/</link>
<description><![CDATA[ <p>The W3 CSS validator is pretty simple to [install locally for use behind the firewall](http://www.emacswiki.org/emacs/FlymakeCSS).

However, by default the validator spits out the whole CSS file after validation, which is inconvenient if your stylesheet is more than a few lines long.

Unfortunately it's not so obvious how to configure the validator to give pretty-printed, human-readable output.  In fact, all there is to it, is to choose a different output format from the several that are supported :)

By default the validator .jar file gives you "text" output, which includes the stylesheet.  To choose a different format, invoke the validator .jar file with an -output argument, like this:

    java -jar css-validator.jar -output  local-file:foo.css

where `` is any of xhtml, xml, text, soap12, json, ucn or gnu

If you just want the errors as (html-escaped) plain text, but without the CSS included, use `gnu`</p> ]]></description>
<pubDate>Wed, 16 Sep 2009 11:53:08 GMT</pubDate>
<guid>http://snipplr.com/view/19817/how-to-configure-the-output-format-of-the-w3-css-validator/</guid>
</item>
<item>
<title>(Ruby) Waiting for events with the Selenium-Client Ruby driver</title>
<link>http://snipplr.com/view/16557/waiting-for-events-with-the-seleniumclient-ruby-driver/</link>
<description><![CDATA[ <p>## List of commonly used `wait_for` commands

For convenience, here are direct links to the documentation of the Selenium-Ruby `wait_for` commands that are most often used.   The [documentation of WaitFor commands in Selenium Core](http://release.seleniumhq.org/selenium-core/1.0.1/reference.html#waitForCondition "WaitForCondition entry in the docs for Selenium Core 1.0.1") may also be of interest.

0. [`wait_for_condition`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000088)
0. [`wait_for_element`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000257)
0. [`wait_for_field_value`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000261)
0. [`wait_for_frame_to_load`](http://selenium-client.rubyforge.org/classes/Selenium/Client/GeneratedDriver.html#M000221)
0. [`wait_for_no_element`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000258)
0. [`wait_for_no_field_value `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000262)
0. [`wait_for_no_text `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000260)
0. [`wait_for_page `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000067)
0. [`wait_for_page_to_load `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000068)
0. [`wait_for_popup `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000069)
0. [`wait_for_text `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000259)

## Where to find the documentation

More information on`wait_for` with the Ruby client, including a complete list of the `wait_for` commands available in the Ruby client, is to be found in the [documentation for the Selenium-Client Ruby Gem.](http://selenium-client.rubyforge.org/ "selenium-client is the official Ruby driver for Selenium RC")  As Selenium-Client defines many "idiomatic" Ruby aliases for built-in Selenium methods, it will probably be especially helpful to become familiar with the [Selenium Ruby driver command set](http://selenium-client.rubyforge.org/classes/Selenium/Client/GeneratedDriver.html) as well as Selenium-Client's [Idiomatic Ruby command set.](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html)

It may also be helpful to refer to the [documentation for Selenium Core](http://release.seleniumhq.org/selenium-core/1.0.1/reference.html#waitForCondition "WaitForCondition entry in the docs for Selenium Core 1.0.1") with regard to `WaitForCondition` and related commands.  In general the **Selenium Core documentation** tends to provide more insight into how commands work, than does the documentation for any of the drivers.

## Examples

Below are a couple of examples of using Selenium's `wait_for` family of commands with the [Ruby driver (Selenium-Client).](http://rubyforge.org/projects/selenium-client/ "Selenium Client Ruby Gem at RubyForge")

One item of note is that , within `wait_for_condition`, one does *not* need to use `this.browserbot.getCurrentWindow()` to access the DOM of the AUT</p> ]]></description>
<pubDate>Wed, 01 Jul 2009 10:57:06 GMT</pubDate>
<guid>http://snipplr.com/view/16557/waiting-for-events-with-the-seleniumclient-ruby-driver/</guid>
</item>
</channel>
</rss>