I suggest you ...

Use existing selector engine from web page instead of injecting sizzle

Understandably, FluentAutomation injects Sizzle into the pages under test so that it can provide us with the wonderful jQuery selector syntax. It then does `window.fluentjQuery = jQuery.noConflict();` so that the previous value of $ is restored and it can then use the "fluentjQuery" object to run DOM queries.

This injection+ noConflict() broke one of my scripts which was expecting a plugin that had been applied to the initial $ and could potentially cause some wonkiness in sites that already have jQuery.

I was able to work around this problem by always having a script on my website that sets fluentjQuery = jQuery. This keeps FluentAutomation from injecting Sizzle and everything stays cool.

Would you kindly consider making it configurable which selector engine (global variable maybe) to use. Or even just have a config that allows the user to prevent injection of Sizzle and just use the existing jQuery or some custom $?

Thanks for listening.

3 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Xeri MajiXeri Maji shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base