Closing this until WebDriver support.
---
Reply to this email directly or view it on GitHub:
https://github.com/watir/watir-webdriver/issues/191#issuecomment-16036554
___
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mai
Closed #191.
---
Reply to this email directly or view it on GitHub:
https://github.com/watir/watir-webdriver/issues/191
___
Wtr-development mailing list
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development
Yes, and, yes, I would hope that this would go into a spec of some sort
(perhaps Ecmascript would be a better place than a w3c spec)
Cheers,
Simon
On Thu, Apr 4, 2013 at 2:16 PM, Alex Rodionov wrote:
> So it should be supported by vendor, correct?
>
> If yes, is there any chance that this wou
So it should be supported by vendor, correct?
If yes, is there any chance that this would be taken care of in W3C spec?
--
Cheerz,
Alex Rodionov
On Thursday, April 4, 2013 at 19:44 , Simon Stewart wrote:
> This feels like something at the level of the WebTiming APIs: it's
> information th
This feels like something at the level of the WebTiming APIs: it's
information that the browser should be exposing in manner that can read by
watir-webdriver via execute_script.
Simon
On Thu, Apr 4, 2013 at 12:23 PM, Jari Bakken wrote:
> selenium-webdriver does not provide any hooks for a clien
selenium-webdriver does not provide any hooks for a client library to inject
code at specific points in the loading process. I think an implementation using
`execute_script` for this will always be unsatisifying, as a lot of errors
would go unnoticed. Because of this, I would prefer to have it a
JSErrorCollector supports only firefox, while the most neat errors usually hide
in ie :smile:
Also, since a lot of apps are Ajax'd, a huge amount of errors can happen after
page is loaded.
---
Reply to this email directly or view it on GitHub:
https://github.com/watir/watir-webdriver/issues/191#
from my experience, problem with js errors is they don't show up on all the
browsers all the time. When a js error happens, they appear only on specific
browsers/version say IE8/IE7 , site not impacted on rest of the browsers,
sometimes only on IE9,etc. Biggest problem of js errors is with IE* w
I think most Javascript errors actually occur before you have a chance to
execute any script from the Ruby side. This can be solved by using a browser
extension, which is the approach taken by
https://github.com/mguillem/JSErrorCollector. I think it would be better to
wrap that in a gem to make
this will be a really useful feature as undetected js errors are one of the
pain points of any e-commerce website!
---
Reply to this email directly or view it on GitHub:
https://github.com/watir/watir-webdriver/issues/191#issuecomment-15885911
___
Wtr-d
I'm thinking about new JavaScript errors API which would work by overwriting
`window.errors` hook and provide a way to retrieve JS errors from page.
So, for example. I enable errors catching:
```ruby
Watir.catch_errors = true
```
Then, we add JavaScript (using `#execute_script`) like the one b
11 matches
Mail list logo
