[
https://issues.apache.org/jira/browse/MYFACES-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649661#comment-17649661
]
Werner Punz edited comment on MYFACES-4538 at 12/20/22 9:55 AM:
----------------------------------------------------------------
Also we will now drop support for old blackberry and winMobile because it did
not work properly to begin with and secondly it would prevent the code
unification given the recent fixes.
There is no way around it sorry, if this causes problems I will recert, but for
now, given both platforms have been dead for ages and at least in winmobile
alternative browsers exist I think it is safe. (Winmobile IE was stuck between
ie5 and 6 with additional bugs, blackberry was even worse)
was (Author: werpu):
Also we will now drop support for old blackberry and winMobile because it did
not work properly to begin with and secondly it would prevent the code
unification given the recent fixes.
There is no way around it sorry, if this causes problems I will recert, but for
now, given both platforms have been dead for ages and at least in winmobile
alternative browsers exist I think it is safe.
> Smaller 2.3 jsf.js code reorganisation to achieve 100% sync between 2.3 and
> 2.3next
> -----------------------------------------------------------------------------------
>
> Key: MYFACES-4538
> URL: https://issues.apache.org/jira/browse/MYFACES-4538
> Project: MyFaces Core
> Issue Type: Task
> Affects Versions: 2.3.10, 2.3-next-M7
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
>
> There has been a diverging of the codebases between 2.3 next 3.0 and master
> going on.
> In order to reduce it, i am improving the 2.3 codebase by shifting additional
> ie6 specific code into quirks.
> Also, the eval code now can be cut down to what we have in the higher
> branches because ie down until 6 (I found some old vms yay...) is supporting
> the head insert method.
> All which is left out are now windows mobile and old blackberry devices. I
> think we can safely make a cut here, if someone has a problem with this we
> still can take the old eval code back in. The rest of the diverting code will
> be shifted into its own quirks package so that we in the future can maintain
> the code more easily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
