[JBoss JIRA] (RF-13155) Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13155?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13155:
-------------------------------
Labels: low_hanging_fruit needs-qe (was: low_hanging_fruit)
> Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13155
> URL: https://issues.jboss.org/browse/RF-13155
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.2
> Environment: Internet Explorer 8
> Reporter: Benoit Pflieger
> Assignee: Brian Leathem
> Priority: Minor
> Labels: low_hanging_fruit, needs-qe
> Fix For: 4.3.4
>
>
> A hidden FileUpload was triggered by clicking an associated label to the generated tag <input type=“file“>.
> That's the security workaround to trigger an <input type=“file“> under Internet Explorer.
> It worked with Richfaces 3.3.
> This workaround can't be achieved anymore with Richfaces 4.3.2 because the <input type=“file“> is only generated without the attribute "id".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13155) Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13155?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13155.
--------------------------------
Assignee: Brian Leathem
Fix Version/s: 4.3.4
Resolution: Done
Added an id attribute to the fileupload input element
> Unable to trigger hidden FileUpload in IE with an associated Label: missing Id on generated <input type=“file“>
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13155
> URL: https://issues.jboss.org/browse/RF-13155
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.2
> Environment: Internet Explorer 8
> Reporter: Benoit Pflieger
> Assignee: Brian Leathem
> Priority: Minor
> Labels: low_hanging_fruit
> Fix For: 4.3.4
>
>
> A hidden FileUpload was triggered by clicking an associated label to the generated tag <input type=“file“>.
> That's the security workaround to trigger an <input type=“file“> under Internet Explorer.
> It worked with Richfaces 3.3.
> This workaround can't be achieved anymore with Richfaces 4.3.2 because the <input type=“file“> is only generated without the attribute "id".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13161) rich:notifyMessages CSS incorrect on MyFaces 2.x
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13161?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13161:
-------------------------------
Fix Version/s: 4.3.4
> rich:notifyMessages CSS incorrect on MyFaces 2.x
> ------------------------------------------------
>
> Key: RF-13161
> URL: https://issues.jboss.org/browse/RF-13161
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final, 4.2.4, 4.3.0.Final, 4.3.1, 4.3.2, 4.3.3
> Reporter: John Yeary
> Labels: myfaces
> Fix For: 4.3.4
>
> Attachments: myfaces-rf-example.zip, myfaces-rf-example.zip, RichfacesNotifyMessagesMyFaces.png
>
>
> The FacesMessage Severity levels do not match between Mojarra and MyFaces. As a result, the CSS styling for INFO messages are one level higher than they should be, and FATAL messages are unstyled.
> *Mojarra* - These represent values 0-3
> {noformat}
> /**
> * <p>Array of all defined values, ascending order of ordinal value.
> * Be sure you include any new instances created above, in the
> * same order.</p>
> */
> private static final Severity[] values =
> { SEVERITY_INFO, SEVERITY_WARN, SEVERITY_ERROR, SEVERITY_FATAL };
> {noformat}
> *MyFaces* - These represent values 1-4
> {noformat}
> /**
> * Message severity level indicating an informational message rather than an error.
> */
> public static final FacesMessage.Severity SEVERITY_INFO = new Severity("Info", 1);
> /**
> * Message severity level indicating that an error might have occurred.
> */
> public static final FacesMessage.Severity SEVERITY_WARN = new Severity("Warn", 2);
> /**
> * Message severity level indicating that an error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_ERROR = new Severity("Error", 3);
> /**
> * Message severity level indicating that a serious error has occurred.
> */
> public static final FacesMessage.Severity SEVERITY_FATAL = new Severity("Fatal", 4);
> {noformat}
> The *<rich:messages/>* component behaves correctly, and may be used as an alternative.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-11469:
---------------------------------
Sample for reproduction in RichFaces 5: https://github.com/richfaces/richfaces/tree/RF-11469-autocomplete-fails-t...
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Brian Leathem
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-11469:
----------------------------
Assignee: Brian Leathem (was: Lukáš Fryč)
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Brian Leathem
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-11469:
---------------------------------
The problem is as [~Trims] described:
* when 3 parameters provided, {{MethodExpression}} created from {{TagAttribute}} in [{{AutocompleteHandler}|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/view/facelets/AutocompleteHandler.java#L51] is used correctly
* when 1 parameter provided, {{MethodExpression}} is created using [{{ExpressionFactory}}|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/AutocompleteRendererBase.java#L106] and even though it should evaluate, it fails
I don't see why it should fail, does anyone have any idea?
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Lukáš Fryč
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-11469:
----------------------------
Comment: was deleted
(was: A comment with security level 'RichFaces Dev' was removed.)
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Lukáš Fryč
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included and only one parameter provided
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-11469:
----------------------------
Summary: autocomplete method does not resolve bean if ui:included and only one parameter provided (was: autocomplete method does not resolve bean if ui:included)
> autocomplete method does not resolve bean if ui:included and only one parameter provided
> ----------------------------------------------------------------------------------------
>
> Key: RF-11469
> URL: https://issues.jboss.org/browse/RF-11469
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Final
> Reporter: u j
> Assignee: Lukáš Fryč
> Priority: Minor
> Attachments: RF-11469.zip
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include.
> {code}
> <ui:include src="/searchlocation.xhtml">
> <ui:param name="bean" value="#{searchBean}" />
> </ui:include>
> {code}
> searchlocation.xhtml contains:
> {code}
> <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" />
> {code}
> The value binding works, but the binding in the autocompleteMethod gives:
> {code}
> 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null
> at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
> at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02]
> at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (RF-13186) Showcase 4.5.x fails
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.s... ]
Michal Petrov updated RF-13186:
-------------------------------
Description:
[https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase
[https://github.com/michpetrov/components/tree/rf4-js] - RF4.5 with updated JS
Builds and deploys fine.
Examples that do not work:
* several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"
* validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
* trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
* menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
* inputs/rich:inplaceInput - ditto
* selects/rich:inplaceSelect - ditto
* output/rich:tooltip - ditto
When resource optimization is turned off the faulty components are missing background image causing a badly generated CSS. {{background-image: url()}} is not handled right by a browser.
was:
[https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase
[https://github.com/michpetrov/components/tree/rf4-js] - RF4.5 with updated JS
Builds and deploys fine.
Examples that do not work:
* several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"
* validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
* trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
* menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
* inputs/rich:inplaceInput - ditto
* selects/rich:inplaceSelect - ditto
* output/rich:tooltip - ditto
* dnd - dragging works, dropping does nothing
When resource optimization is turned off the faulty components are missing background image causing a badly generated CSS. {{background-image: url()}} is not handled right by a browser.
> Showcase 4.5.x fails
> --------------------
>
> Key: RF-13186
> URL: https://issues.jboss.org/browse/RF-13186
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase
> [https://github.com/michpetrov/components/tree/rf4-js] - RF4.5 with updated JS
> Builds and deploys fine.
> Examples that do not work:
> * several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization is turned off the faulty components are missing background image causing a badly generated CSS. {{background-image: url()}} is not handled right by a browser.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months