It is not possible to use eps 1.7.0 version with ember-cli-page-object
See original GitHub issueAs i understand the root of the problem is deprecation of :eq()
selector
when using collections in ember-cli-page-object
it generates selectors which looks something like this
.some-collection .some-collection-item:eq(0) .power-select-container .ember-power-select-trigger
and i pass this selector to selectChoose
helper and it results error because selectChoose calls querySelector which does not support :eq
Any ideas how to solve this?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Support for EPS images has been turned off in Office
It will no longer be possible for subscribers to insert EPS files in Office documents by any means. It looks like a product...
Read more >Converted xxx-eps-converted-to.pdf not found - TeX
I'm using TeXStudio on Mac OS X 10.7. 4. The problem is that the EPS to PDF conversion is somehow broken: \usepackage[pdftex]{graphicx} \graphicspath{{img/}}...
Read more >Cannot open EPS files in illustrator - Adobe Support Community
We have over 1000 customers using EPS so they are not likely to change and we ... Create a new file in your...
Read more >Encapsulated PostScript (EPS) File Format, Version 3.x
The compilers of this resource have not been able to determine whether the other preview variants are still in use. Comments welcome.
Read more >Why does MATLAB not export EPS files properly? - MathWorks
As you are likely using a bitmap renderer, MATLAB has to first convert the bitmap into a vector, and this conversion of bitmaps...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Sinled I’ve done that already. Now you can find the trigger using jQuery specific selectors and pass it to the
selectChoose
helper as above. Released in 1.7.1.Will that help?
You’re right. This is because the addon stopped relying in jQuery.
One improvement that it’s easy enough and would “fix” your problem would be to improve the
selectChoose
helper to accept anHTMLElement
as first argument instead of a string. What way you can still use jQuery specific stuff to find the trigger and pass it to the helper.E.g: