This isn't so much an issue as it is a question about a potential issue. In using Capypage, what's the preferred idiom for accessing elements in an iframe? Or more generally the idea of the "within" construct from Capybara.

Right now the selector has to be explicit i.e.

element :foo, "#foo"

Add a convention so that by default the element name is same as the ID of the equivalent html element. So if I have an element with id=foo, capypage should default to use that for selection.

Getting the following exception when using # frozen_string_literal: true

Error Message: can't modify frozen String
Stacktrace:
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `gsub!'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `block (2 levels) in load'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `each'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `block in load'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `tap'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:39:in `load'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:34:in `tap'
/usr/local/lib/ruby/gems/2.3.0/gems/capypage-0.2.7/lib/capypage/page.rb:34:in `visit'

Hi,

When i try to update capybara gem, i am getting the below message

capypage was resolved to 0.2.6, which depends on
      capybara (~> 2.1.0)

Could you please make capypage support to latest versions of capybara?

Thanks,
Gowtham

I have a scenario to locate an element by its containing text.
For example,
page.find("#product",:text => "shampoo")
How can I define this element in Capypage?