(Alex/Alexey) Aleksei (Stree’Jacque) Strizhak
(Alex/Alexey) Aleksei (Stree’Jacque) Strizhak
> more intelligent Sounds nice, it looks like for now this is something like _wrong behavior_: ``` [1] pry(main)> require "addressable" => true [2] pry(main)> uri = Addressable::URI.parse("http://www.google.com/?test=original") => #...
Hello @dsisnero this PR is on review, it can't be merged without approval. The linter offenses are not related to this particular PR, we have dedicated PR to solve it:...
@zw963 > How to check one node is visible by user? Maybe this may help: https://github.com/rubycdp/ferrum/pull/141 We can try using this CDP command to click on invisible elements: https://chromedevtools.github.io/devtools-protocol/tot/DOM/#method-scrollIntoViewIfNeeded By...
> If this API? please check screenshot. correct. > it always work before because Capybara have this functionality, right? yes, but it uses cuprite underneath as driver: https://github.com/rubycdp/cuprite/blob/749805654986d832554ffd17bb3f190159ed2b3e/lib/capybara/cuprite/page.rb#L95-L96
> Is there a way to port this feature into ferrum directly? we wanna keep ferrum as simple as possible: > ferrum instead should be close to what real user...
> I would like to keep it this way so as not to break the existing code of many users. well if it is a not quite expected behavior which...
Hi @RanVaknin, thank you for letting me know, I hope it would be sorted soon by return refresh token according to documentation :+1: .
@stfnio > Which linter rule is in charge here? ![Selection_896](https://user-images.githubusercontent.com/23525618/138401332-3086a46c-07fd-4d63-850c-249561c09a81.jpg) https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/no-settled-after-test-helper.md I suspect, in your case, the action that binds on click contains the promise that is not resolved before...
any updates here? I got the same issue on Ember 3.0.0 after the upgrade `ember-power-select-typeahead` from `0.6.1` to `0.7.4`. Is it possible to use some workaround to keep "else" logic-branch?
well, afaik it's good to avoid the using of inheritance in this way. take a look at these notes: https://github.com/serodriguez68/poodr-notes#coding-technique-6-create-shallow-hierarchies By the way, the case when we need shared settings...