-
Notifications
You must be signed in to change notification settings - Fork 71
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
Feature/myfaces 4466 faces.js reimplementation (target 4.0.0 RC4) #356
Conversation
…ES-4456 # Conflicts: # api/src/main/javascript/META-INF/resources/myfaces/_impl/xhrCore/_AjaxUtils.js
* MYFACES-4468: Implement f:selectItemGroup * Create test for f:selectItemGroup * Resolve TCK signature failures (Remove Added Fields)
…ing import ranges in manifest
nonce handling in the new tests
integrated dom query sources, another fix for the nonce handling
updating from the github upstream project. Fix for an eval regression introduced by our nonce fixes (only the new codebase is affected) integratioin test 5, double eval failed because of it
updating to the latest mona-dish (no fixes but just to be in sync)
# Conflicts: # api/src/main/javascript/META-INF/resources/myfaces/_impl/_util/_Dom.js # api/src/main/javascript/META-INF/resources/myfaces/_impl/core/_EvalHandlers.js # api/src/main/javascript/META-INF/resources/myfaces/_impl/core/_Runtime.js
Yikes OK then I will leave it up to @tandraschko @volosied what they want to do. Sounds like this could be tricky/messy. |
Yes thats the reason why I started with the selenium port of the TCK to begin with, to get the tests out of the tech dead end they obviously have been for quite a while. Selenium simply is under active development and has strong corporate backing. |
Hi, let me find out if there's been any progress or testing done with the Selenium TCK PR (1732) yet. |
Hi I just noticed i ported from a rather old branch (4.0.1) there have been many bugfixes going into the TCK, so I will have te Re-port again and update the pull request accordingly. This will happen until sometime next week. |
I will resolve the conflicts next week, they are related to my work on MYFACES-4526, MYFACES-4040 |
@werpu I really appreciate all your work on this! |
Says there are conflicts? |
Hi I have reopened the tck ajax pull request, this time against the proper branch jakartaee/faces#1770 Lets see if they take it in! |
Not sure what the problem atm is by showing me conflicts... the branches are in sync but github is giving me sync problems to my private fork |
I would like to see this merged |
Hi following: The question now is after that how we proceed. The TCKs pass as well as with the old codebase, but with the selenium version. If that is good enough for being able to say we are TCK compliant, then I am fine. On the TS side I want to do a cleanup of the XHRFormData the upcoming weeks, the aim is to reduce complexity (it has grown too complex for my liking and has a ton of simplification potential), but that is independent of the merge! |
what about:
WDYT @volosied @melloware @pnicolucci ? |
I like that idea. |
MYFACES-4517 is a duplicate of MYFACES-4425 This test was challenged and accepted: MYFACES-4489 was also challenged: |
if they are challenged and closed, please lets just close our JIRA issues |
As I said my cleanup is independent of anything... we can do it before or after. Preferrably before. I just did the major merge and have pushed it. |
Sorry for the delay, but I was held up work related issues. https://gist.github.com/werpu/47ef2a062e82032551706b9effed316d I have to investigate a file upload issue reported by the Tobago guys, but once they give the ok, I will be ready to merge. |
All the changes are merged in, waiting for the final test of the Tobago people, TCK tests pass! Note, seems like the pull request is lost in git, we will have to reopen a new one before the merge, here is the commit: and here the full branch, as you can see no conflicts: |
@volosied @tandraschko, I have yet to check the status, but it seems like the selenium based tests are now part of the official TCK, how about a merge of this early next week? |
+1 from my side |
I discovered a selectOneRadio bug caused by one of my changes. I am working to fix it now (will make a JIRA soon). |
I think an RC5 is the best bet to roll up all the changes then we can run everything against the TCK. Then do a 4.0.0 release. |
The Tobago guys also gave my internal jsf_ts RC.33 the ok which is the build the last downstream merge is based on! |
Closing this now, I have opened another pull request: #514 Please continue the discussion there |
had to recreate the pull request because i had to rename the branch