[JBoss JIRA] (RF-12766) Metamer: a4j:log doesn't work with popup option
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12766?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak resolved RF-12766.
--------------------------------
Resolution: Cannot Reproduce Bug
Works fine in both 4.2.3.Final and 4.3.0.Final. However, popup window doesn't open in Firefox because of Firebug (see RF-12799)
> Metamer: a4j:log doesn't work with popup option
> -----------------------------------------------
>
> Key: RF-12766
> URL: https://issues.jboss.org/browse/RF-12766
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.0.3, JPP 6.0 EPP 05, Firefox 18.0.1
> Reporter: Petr Mensik
> Labels: a4j:log, jpp-6.0, metamer, portletbridge, richfaces
> Fix For: 4.3.1
>
>
> This bug is connected with a4j:log component. When you set a mode attribute to popup and then do some action, nothing happens.
--
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
11 years, 4 months
[JBoss JIRA] (RF-12799) Log: add attribute hotkey
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-12799:
----------------------------------
Summary: Log: add attribute hotkey
Key: RF-12799
URL: https://issues.jboss.org/browse/RF-12799
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.0.Final
Reporter: Pavol Pitonak
a4j:log doesn't work in popup mode in Firefox with installed Firebug because they both use the same keyboard shortcuts (Ctrl+Shift+L). a4j:log in RichFaces 3.3.x had attribute "hotkey" which changed shortcut to Ctrl+Shift+<your_choice>.
--
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
11 years, 4 months
[JBoss JIRA] (RF-12798) <a4j:push>: parameter to enable JMS integration
by Roberto Contiero (JIRA)
Roberto Contiero created RF-12798:
-------------------------------------
Summary: <a4j:push>: parameter to enable JMS integration
Key: RF-12798
URL: https://issues.jboss.org/browse/RF-12798
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: doc
Affects Versions: 4.3.0.Final
Reporter: Roberto Contiero
Priority: Minor
There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't:
<context-param>
<param-name>org.richfaces.push.jms.enable</param-name>
<param-value>true</param-value>
</context-param>
but
<context-param>
<param-name>org.richfaces.push.jms.enabled</param-name>
<param-value>true</param-value>
</context-param>
--
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
11 years, 4 months
[JBoss JIRA] (RF-12774) a4j:commandLink does not set the styleClass when disabled
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12774?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-12774.
-----------------------------
Resolution: Done
> a4j:commandLink does not set the styleClass when disabled
> ---------------------------------------------------------
>
> Key: RF-12774
> URL: https://issues.jboss.org/browse/RF-12774
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.0.Final
> Reporter: Timothy Whitehead
> Assignee: Lukáš Fryč
> Labels: a4j:commandLink, regression, richfaces, styleClass
> Fix For: 4.3.1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> I upgraded to 4.3.0.Final and when I use a disabled a4j:commandLink it renders with class="class org.richfaces.component.UICommandLink" I believe it was working correctly in 4.2.3.Final
--
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
11 years, 4 months