-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Click on an anchor element with child image element threw error #19
Comments
I think a work-around would be to change the image markup to use CSS background instead. |
Can you provide steps to reproduce?, from the stack trace i see that this is happening with behat. Maybe is the way behat selects the "unique-id" element and sends the clic to GastonJS |
I am using angular.js as a front-end app on this page, and the element has When I have the time, I'll try to come up with a distributable/workable example that fails. Thank you for your response. |
I'm seeing this with a fairly simple scenario. I tested with both version 1.9.8 and 2.1.1 versions of phantomjs with no difference in results. It seems timing related. I figured it is because the DOM isn't visible, so I added this to the behat test: Where it is failing is on my call to Here's the full step that fails.
|
So far i can see that PhantomJS crashes and that mostly points to a bug on PhantomJS, although @heddn has a point and seems a timing issue due to the Edit not being visible. |
Unfortunately, I'm doing this in Drupal and it is for a client site. But one place I'm able to recreate it consistently is with ckeditor loading on a page. I used to do |
@heddn Thanks for the info, i'll try to create a full defined steps to reproduce in order to either fix gastonJS code or to post an error to PhantomJS repo. |
You can reproduce this problem by adding Test: https://www.drupal.org/files/issues/drupal-2773791-5-test-only.patch |
@mortenson thanks a lot, this will help to quickly debug and see whether gastonjs needs code change or is a weird behaviour with phantomjs. |
@jcalderonzumba did you have any luck debugging this issue based on #19 (comment) |
@tedbow No, unfortunately my current job does not allow me much free time other than weekends. |
@mradcliffe How did you solve this problem? |
I didn't solve the issue, @maporto. I have a behat.yml that can switch between browsers (including using phantom), and run tests using Chrome and Firefox. |
Error output said to report the bug so I'm reporting it.
Given I have an anchor element similar to
Then I should be able to call click on it using
id|name|title|alt|value
.I got the following error trying
I click :link
using the title or id attributes on the anchor element.The text was updated successfully, but these errors were encountered: