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
LPS-122449 Remove usages of dom.delegate #466
Conversation
MDN's page on
|
97ecbc9
to
7d86fe8
Compare
I've pushed another batch of changes, and updated the list of those I didn't manage to test due to not being able to find them in the UI. I've hit a problem with one of them, upload_multiple_file_entries_resources.jsp, where after adding delegate, and doing the thing that triggers the event the page breaks, and it cannot find |
7d86fe8
to
041ccf8
Compare
I've pushed more changes here, but there's a blocker that I explained in Slack. |
041ccf8
to
fbe0b4a
Compare
I've pushed a couple commits, replacing old ones. One of the commits expands the P.S. is there a way to globally run |
...end-js/frontend-js-web/src/main/resources/META-INF/resources/liferay/delegate/delegate.es.js
Outdated
Show resolved
Hide resolved
fbe0b4a
to
c0c410d
Compare
I've pushed new commits, removing the old ones, the commits are split into 2, one for JSPs and one for JS files. I've tested a couple of patterns used in JSPs and one (and only) pattern used in JS files. |
GitHub is showing conflicts on this one @kresimir-coko, so looks like it needs a rebase. |
I see @wincent thanks for the ping, I'll take a look. |
c0c410d
to
6a65c90
Compare
Hey @wincent I've pushed commits with removed conflicts! |
ci:test:sf |
ci:test:relevant |
❌ ci:test:sf - 0 out of 1 jobs passed in 22 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-122449 1 Failed Jobs:For more details click here.
|
Jenkins Build:test-portal-source-format#4307 |
Hey @wincent I'm trying to see which files/modules have SF errors in them, but I don't know the login details for the test platform: |
Hey @kresimir-coko, just expand the comment above: And locally run |
Didn't know we had this going for us, awesome, ran it and pushed a commit fixing those SF problems. |
At least some of them can be seen in the GitHub comment:
but in any case, the login details are your Liferay email address name (ie. up to but not including the |
ci:test:sf |
✔️ ci:test:stable - 9 out of 9 jobs passed❌ ci:test:relevant - 19 out of 30 jobs passed in 2 hours 53 minutesClick here for more details.Base Branch:Branch Name: master Copied in Private Modules Branch:Branch Name: master-private ci:test:stable - 9 out of 9 jobs PASSED9 Successful Jobs:
ci:test:relevant - 19 out of 30 jobs PASSED11 Failed Jobs:
19 Successful Jobs:
For more details click here.Failures unique to this pull:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#9173 |
Hey @john-co I've fixed the problem in the Related section you mentioned, leftover CI errors are probably not related to this PR, can you confirm? |
cc/ @cvanut, can you please take a look? The failing tests look like they're all Forms tests. |
pinged Cleyton on slack to advise. |
Cleyton says he will take a look tomorrow. |
Hey @kresimir-coko, could you rebase this in the meantime? In the future, it's best to split these tasks in different commits so you can discard whatever area is giving you trouble to avoid the whole thing getting blocked over an issue in one specific area. If you want, you could actually rework this PR to split the changes in Forms from the rest and send 2 different PRs to see if you can get something going. |
@jbalsas Sure, I'm fixing conflicts as we speak, so I'll split Forms away and send 2 separate PRs |
Just started reviewing :) |
Here's the differences I'm seeing when running poshi test from this PR test bundle: After clicking the Close (x) icon from the side panel, the Text Field is still highlighted (border focused). And then when the test clicks on the Plus button again, the side panel is supposed to show Elements tab to add another element, but instead has Basics tab which edits the Text Field. You can see from the video from the master bundle that the Text Field is not highligted (border focused). And then when it clicks on Plus button, it correctly shows the side panel with Elements tab in order to add another element. There's no difference between Chrome 86 and 65. I was able to reproduce the issue on both chrome versions running the poshi test locally. However, I cannot reproduce the issue manually. With the current tools we have I can think of including a refresh page, or navigating back to the page as a good hard reset for a test fix workaround. Could this be resolved on the poshi side @kenjiheigel? Maybe there's some dependent behavior with dom.delegate? |
Going to close this since we're apparently trying to split it into smaller PRs like #466 😉 |
I've started removing usages of
dom.delegate
.In the meanwhile I realised that the implementation of
delegate
isn't fully functional, at least from my investigations, so I've pushed a commit that extends the utility to find an ancestor that matches the providedselector
.I've also provided some examples of usage with the pattern tested working, except a couple of them - ones that have selectors for html tags or children, e.g.
'.someClassName a'