[JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13638:
-----------------------------
Labels: (was: needs)
> Upgrade CKEditor to 4.3
> -----------------------
>
> Key: RF-13638
> URL: https://issues.jboss.org/browse/RF-13638
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4, 5.0.0.Alpha1
> Reporter: barbara b
> Assignee: Lukáš Fryč
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13638:
-----------------------------
Labels: needs (was: )
> Upgrade CKEditor to 4.3
> -----------------------
>
> Key: RF-13638
> URL: https://issues.jboss.org/browse/RF-13638
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4, 5.0.0.Alpha1
> Reporter: barbara b
> Assignee: Lukáš Fryč
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13646) Fix resource optimization
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13646?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13646.
----------------------------
Verified. Closing.
> Fix resource optimization
> -------------------------
>
> Key: RF-13646
> URL: https://issues.jboss.org/browse/RF-13646
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Michal Petrov
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> # There are some resource files that are not being generated (e.g. gradientA.png). It's either a generation or optimization issue.
> # -The optimization settings need to be updated, core files are currently not being packed (legacy of RF 4.5/RF 5 source collision avoidance)-
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13649) TogglePanel: fails to render meta-component '@header'
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13649?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13649.
----------------------------
Verified. Closing.
> TogglePanel: fails to render meta-component '@header'
> -----------------------------------------------------
>
> Key: RF-13649
> URL: https://issues.jboss.org/browse/RF-13649
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.5.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> The issue is here: [{{header != activeItem}}|https://github.com/richfaces/richfaces/blob/0733e3d0d76ca7df...]
> Server stack trace:
> {code}
> 09:31:06,859 SEVERE [org.richfaces.log.Context] (default task-12) header: java.lang.IllegalArgumentException: header
> at org.richfaces.renderkit.html.TogglePanelRenderer.encodeMetaComponent(TogglePanelRenderer.java:192) [richfaces.jar:4.5.0-SNAPSHOT]
> at org.richfaces.component.AbstractTogglePanel.encodeMetaComponent(AbstractTogglePanel.java:891) [richfaces.jar:4.5.0-SNAPSHOT]
> at org.richfaces.context.MetaComponentEncodingVisitCallback.visit(MetaComponentEncodingVisitCallback.java:69) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
> at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:103) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
> at org.richfaces.context.ExtendedRenderVisitContext.invokeVisitCallback(ExtendedRenderVisitContext.java:65) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
> at org.richfaces.context.ExtendedVisitContext.invokeMetaComponentVisitCallback(ExtendedVisitContext.java:76) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
> at org.richfaces.component.AbstractTabPanel.visitMetaComponents(AbstractTabPanel.java:150) [richfaces.jar:4.5.0-SNAPSHOT]
> at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:915) [richfaces.jar:4.5.0-SNAPSHOT]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at com.sun.faces.context.PartialViewContextImpl.processComponents(PartialViewContextImpl.java:406) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.context.PartialViewContextImpl.processPartial(PartialViewContextImpl.java:325) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at org.richfaces.context.ExtendedPartialViewContext.processPartial(ExtendedPartialViewContext.java:254) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT]
> at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:1004) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1856) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:435) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:133) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) [jsf-impl-2.2.5-jbossorg-3.jar:]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5]
> {code}
> The issue is reproducible by [ITStaticTab|https://github.com/richfaces/richfaces/blob/0733e3d0d76ca7dfb...] test
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek reopened RF-11741:
------------------------------
Assignee: Brian Leathem
[~bleathem], I have added a reproducer to Metamer. I used the same ecss as in decription:
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
At the end (accessible from browser) the css looked like this:
{code}
*.shadow {
-webkit-box-shadow: 4px 4px 5px "#ECF4FE";
-moz-box-shadow: 4px 4px 5px "#ECF4FE";
box-shadow: 4px 4px 5px "#ECF4FE";
}
{code}
In the result, this ecss file will not work because of the inserted {{""}} to the css file. Is there any way how to prevent inserting of these quotation marks?
Verified in 4.5 Metamer on FF 30, Chrome 35 and on EAP 6.3.0.ER8.
-----
Just to verify, I have also tried to hardcode the same values without the quotation marks in the ecss, like this:
{code}
.shadow{
-webkit-box-shadow: 40px 40px 50px #ECF4FE;
-moz-box-shadow: 40px 40px 50px #ECF4FE;
box-shadow: 40px 40px 50px #ECF4FE;
}
{code}
The panel had the shadow and the final css was:
{code}
*.shadow {
-webkit-box-shadow: 40px 40px 50px rgb(236, 244, 254);
-moz-box-shadow: 40px 40px 50px rgb(236, 244, 254);
box-shadow: 40px 40px 50px rgb(236, 244, 254);
}
{code}
The Metamer sample is accessible from http://localhost:8080/metamer/faces/components/skinning/rf-11741.xhtml.
If this cannot be fixed, please resolve and close this issue.
> ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely
> ------------------------------------------------------------------------------------------------------
>
> Key: RF-11741
> URL: https://issues.jboss.org/browse/RF-11741
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: skinning
> Affects Versions: 4.1.0.CR1
> Reporter: Karsten Wutzke
> Assignee: Brian Leathem
> Labels: ecss, parsing, skinning
> Fix For: 4.5.0.Alpha3
>
>
> When defining rules like
> {code}
> .shadow
> {
> -webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
> -moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
> box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
> }
> {code}
> in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule entirely and no shadows will be rendered. BTW it would be better to just omit the invalid properties instead of the entire selector (box-shadow: ... alone works).
> Most browsers don't support the box-shadow yet, so defining proprietary properties *must* be possible. Note, this applies to a lot more properties than the above.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13514) Support file upload progress tracking in Servlets >= 3.0 environment
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.s... ]
Matej Novotny closed RF-13514.
------------------------------
Verified, closing issue.
> Support file upload progress tracking in Servlets >= 3.0 environment
> --------------------------------------------------------------------
>
> Key: RF-13514
> URL: https://issues.jboss.org/browse/RF-13514
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-input, core
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We currently support two approaches for file upload:
> * Servlets 2.5: own request form data parser [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java]
> * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}}
> However as we have discussed RF-13444, we had to finally do a trade-off of limiting support of file progress tracking. I.e. in Servlets 3.0 we have no simple way how to track file upload progress since getParts() returns data for completed request.
> There are several possible outcomes:
> 1) drop server-side file upload progress tracking and leverage XHR2/HTML5 that has built-in ability to track progress
> * imho we are already prepared to switch to XHR2 and client-side progress (possibly leveraging some third-party widget) since [all major browsers support it at least one version back|http://caniuse.com/#feat=xhr2]
> * existing implementation: http://www.script-tutorials.com/pure-html5-file-upload/
> 2) use a {{ServletFilter}} to wrap a request as our {{FileUploadFacesContextFactory}} currently do and so have an earlier access to the request object
> * this principle has a drawback - we have to ensure our filter has high-enough priority so the servlet container won't touch the request body yet
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13650) ITResourceOptimization tests fail - no resource aggregation applied
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13650?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13650.
----------------------------
Verified. Closing.
> ITResourceOptimization tests fail - no resource aggregation applied
> -------------------------------------------------------------------
>
> Key: RF-13650
> URL: https://issues.jboss.org/browse/RF-13650
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 4.5.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> {code}
> TResourceOptimization.test_script_packaging:104 expected:<1> but was:<0>
> ITResourceOptimization.test_stylesheet_packaging:113 expected:<1> but was:<0>
> {code}
> Originally revealed by RF-13591
> These are smoke tests ,we should address them in 4.5.0.Alpha3.
> ----
> Here is the source of the page generated by {{test_script_packaging}}:
> {code}
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:s="http://richfaces.org/sandbox/prototyping">
> <head id="j_idt3">
> <style>body {background: white;}</style>
> <script type="text/javascript" src="/ITResourceOptimization/javax.faces.resource/jsf.js.jsf?ln=javax.faces"></script><script type="text/javascript" src="/ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces/jquery.js"></script><script type="text/javascript" src="/ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces/richfaces.js"></script>
> <link type="text/css" rel="stylesheet" href="/ITResourceOptimization/org.richfaces.resources/javax.faces.resource/org.richfaces/skinning.ecss?db=eAG7dPvZfwAIqAOT" />
> </head>
> <body></body>
> </html>
> {code}
> As you can see, there is {{richfaces.js}} in the head section, but actual aggregated resource (like ({{core.js}}) is expected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RF-13597) Drag and drop support for file upload
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13597?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13597:
------------------------------------
Dropping files onto the add button is not the intended use. The add button contains the <input type="file">, some browsers allow dropping the files directly onto the input element, some do not. I don't think that functionality can be changed. Extending the dropzone might interfere with this, I'll look into it.
> Drag and drop support for file upload
> -------------------------------------
>
> Key: RF-13597
> URL: https://issues.jboss.org/browse/RF-13597
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 4.1.0.Final
> Reporter: abhishek vijra
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Drag/Drop support should be added to file upload component .
> Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months