[jira] [Commented] (MYFACES-4522) jsf.js sync the 2.3-next files back into 2.3

["Werner Punz (Jira)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644305#comment-17644305 ] 

Werner Punz commented on MYFACES-4522:
--------------------------------------

Ok I was wrong... 2.3next has a different agenda, we basically cut off a ton of old browser support in 2.3 next.

Thing is the baseline of 2.3next is ie9 so still very old.

I would not have any problem to sync this code back into 2.3, but I cannot decide that alone.

I just do not want to maintain another even older codebase anymore.

2.3 Next back then was founded to get rid of some legacy code.

My proposal is to keep 2.3next and 2.3 in sync regarding the js codebase for now, but increase the baseline for the supported browsers for 2.3next to ie9!

 

> jsf.js sync the 2.3-next files back into 2.3
> --------------------------------------------
>
>                 Key: MYFACES-4522
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4522
>             Project: MyFaces Core
>          Issue Type: Task
>    Affects Versions: 2.3.10
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>            Priority: Major
>
> We have had a ton of fixes in the old codebase which made it so far into 2.3-next and 4.0
> however given that 2.3 still is in active development we should sync those changes back into the 2.3 branch. Given 2.3-next and 2.3 share the same code on JS level, a simple diff should suffice instead of cherry picking every fix.
> I will make a single commit under this issue for 2.3



--
This message was sent by Atlassian Jira
(v8.20.10#820010)