I want to verify that I understand the proposal.

Is the suggestion that the Watir-WebDriver API be added to the IE driver in
addition to the existing API? Or will it replace it, creating backwards
incompatability?

Bret

On Fri, Dec 31, 2010 at 8:42 AM, Jarmo <[email protected]> wrote:

> I myself like the Watir-WebDriver solution a little more because there you
> have to specify exact CSS property and not some pseudo-property, e.g.
> backgroundImage vs background-image. Yes, the backgroundImage is part of the
> IE API, but as Jari pointed out already it's leaky solution and fights
> against standards.
>
> Jarmo
>
> On Fri, Dec 31, 2010 at 4:24 PM, Aliaksandr Ikhelis <
> [email protected]> wrote:
>
>> Hi All,
>>
>> Just wanted to raise a style() method question here. Apologize if it was
>> already discussed before.
>>
>> Getting a style element works differently with Watir and watir-webdriver.
>>
>> Watir:
>> element.style.backgroundImage
>>
>> Watir-WebDriver:
>> element.style("background-image")
>> Watir is giving you direct access to a COM object, which is a leaky
>> abstraction and should not be part of the Watir API. Instead, we should
>> decide on a common API that can be implemented without leaking
>> implementation details.
>> The issue and solution proposed by Jari are described in more details
>> here: https://github.com/jarib/watir-webdriver/issues/closed#issue/11
>>
>> Thank you,
>> Aliaksandr Ikhelis
>>
>> _______________________________________________
>> Wtr-development mailing list
>> [email protected]
>> http://rubyforge.org/mailman/listinfo/wtr-development
>>
>
>
> _______________________________________________
> Wtr-development mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/wtr-development
>



-- 
Bret Pettichord
Lead Developer, Watir, www.watir.com

Blog, www.io.com/~wazmo/blog
Twitter, www.twitter.com/bpettichord
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to