Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWhy the xpath? it just makes it impossbile to see what your code is doing, and also makes it very brittle, changes to the layout of the page are going to make that break all the time. xpath is horrid stuff, only use it if nothing else works. On the page you gave there's a handy ID value for the div that holds the stuff that does the slider range, and it looks pretty static (more static than the nesting of the divs on the page. Why not use `browser.div(:id => 'slider-range').link(:index => 1).send_keys :arrow_right' instead?
      singulars
    2. COare you a reforming Selenium user? (just curious) it seems like people who are used to Selenium get addicted to selecting stuff via these hidious xpath expressions that are brittle as hell and hard to read. I mean seriously two months from now, will you have ANY clue what element is being interacted with there? and how long will it take you to trace it down via the DOM.. compare that to using the Watir api properly, where you can immediately identify which div holds the control you are sending keys to..
      singulars
    3. COI'm a Watir user and have never really used Selenium to the level I use watir-webdriver. I totally understand where your coming from. I always do my coding by showing the actual elements. Just used xpath for this particular example. (Won't make same mistake again). Anyway once again thank you very much for the feedback and I have taken aboard the advice that you have passed on. Will try to stay away from xpath
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload