[JBoss JIRA] (RF-12849) Showcase - update readme - remove obsolete, add new
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12849?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12849:
-------------------------------
Fix Version/s: 4.3.2
> Showcase - update readme - remove obsolete, add new
> ---------------------------------------------------
>
> Key: RF-12849
> URL: https://issues.jboss.org/browse/RF-12849
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.1
> Reporter: Juraj Húska
> Fix For: 4.3.2
>
>
> After rewriting showcase readme to markdown syntax I would update it for example with following:
> * reference to showcase online demo
> * remove publishing to GAE and put there publishing to Openshift instead
> * I would create small clickable TOC in the top of the page
> * remove deploying on JBoss AS 6 and maybe add deploying on EAP 6 (it is now available to download)
> * Mention JBDS as an option
--
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, 3 months
[JBoss JIRA] (RF-12848) Error "source is not defined" after richfaces-jsf-event.js merge
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12848?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12848:
----------------------------------
Assignee: Lukáš Fryč
Please assess and schedule as required.
> Error "source is not defined" after richfaces-jsf-event.js merge
> ----------------------------------------------------------------
>
> Key: RF-12848
> URL: https://issues.jboss.org/browse/RF-12848
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.3.1
> Reporter: Torben Greiser
> Assignee: Lukáš Fryč
>
> Commit 9255380d626227d909bbcd59ea3bc604966ea5bb breaks the following jsf.ajax.request:
> {code}
> jsf.ajax.request("MyContainer:MySelectionForm", "valueChange", {});
> {code}
> In <a4j:log/> the following error is displayed:
> {code}
> richfaces.queue: ajax submit error: source is not defined
> {code}
> After inspecting richfaces.js I located the cause of the error:
> {code}
> var getFormElement = function(sourceElement) {
> if ($(sourceElement).is('form')) {
> return source;
> } else {
> return $('form').has(sourceElement).get(0);
> }
> };
> {code}
> First if-statement evaluates to true, returning source, which itself is not defined:
> {code}
> ReferenceError: source is not defined
> {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
11 years, 3 months
[JBoss JIRA] (RF-12849) Showcase - update readme - remove obsolete, add new
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12849?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12849:
------------------------------------
[~jhuska] that would be great if you could make these additions. Thanks!
> Showcase - update readme - remove obsolete, add new
> ---------------------------------------------------
>
> Key: RF-12849
> URL: https://issues.jboss.org/browse/RF-12849
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.1
> Reporter: Juraj Húska
>
> After rewriting showcase readme to markdown syntax I would update it for example with following:
> * reference to showcase online demo
> * remove publishing to GAE and put there publishing to Openshift instead
> * I would create small clickable TOC in the top of the page
> * remove deploying on JBoss AS 6 and maybe add deploying on EAP 6 (it is now available to download)
> * Mention JBDS as an option
--
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, 3 months
[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12846:
------------------------------------
Have you tried using the _<rich:hotkey>_ component?
> a4j:commandLink accesskey attribute missing
> -------------------------------------------
>
> Key: RF-12846
> URL: https://issues.jboss.org/browse/RF-12846
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1
> Reporter: John Yeary
> Priority: Minor
>
> The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE.
--
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, 3 months
[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12846:
-------------------------------
Labels: waiting_on_user (was: )
> a4j:commandLink accesskey attribute missing
> -------------------------------------------
>
> Key: RF-12846
> URL: https://issues.jboss.org/browse/RF-12846
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1
> Reporter: John Yeary
> Priority: Minor
> Labels: waiting_on_user
>
> The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE.
--
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, 3 months
[JBoss JIRA] (RF-12841) Tooltip: JavaScript Error with showDelay and partial update
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12841?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12841:
----------------------------------
Assignee: Pavol Pitonak
Pavol, please verify.
> Tooltip: JavaScript Error with showDelay and partial update
> -----------------------------------------------------------
>
> Key: RF-12841
> URL: https://issues.jboss.org/browse/RF-12841
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.Final, 4.3.1
> Environment: Mojarra 2.1.17
> Reporter: Lutz Ulrich
> Assignee: Pavol Pitonak
> Priority: Minor
>
> rich:tooltip causes script error when showDelay is used and the tooltip is updated due to a JSF request.
> Console log of Firefox:
> TypeError: tooltip.popup is null
> tooltip.popup.show(tooltip.saveShowEvent); in tooltip.js (line 245)
> The error comes in all browsers I tested with.
> {code}
> <a4j:commandLink action="#{richTabMinimizer.toggle}" render="@this">
> <h:graphicImage library="org.richfaces.images"
> name="#{richTabMinimizer.expanded ? 'triangleUp.png' : 'triangleDown.png'}"/>
>
> <rich:tooltip followMouse="false" showDelay="1000">
> #{richTabMinimizer.expanded ? 'close' : 'expand'}
> </rich:tooltip>
> </a4j:commandLink>
>
> {code}
> (Its a stripped down example. The actual content of my tool-tip holds more text.)
> Note that my 'richTabMinimizer.toggle' bean toggles some GUI stuff and its property 'expanded' is switched from true to false and vice versa.
> You may probably replace it with anything to reproduce the error.
> Probably the tool-tip tries to show after the HTML elements have already been updated.
> It's no serious error. Nevertheless, its ugly.
> I guess it is not unusual to have a tool-tip (with a showDelay) on a command.
> But often, users will click the command just after the mouse entered the command.
> Maybe this issue report is a duplicate of RF-8652, but in contrast to 8652, I do not refer to open tooltips.
> For me, it would be sufficient if the script error is avoided.
> I do not expect the updated tooltip to show after the delay.
--
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, 3 months
[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes don't work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12839:
------------------------------------
Pavol, how many of those attributes not working are regressions? Only oncomplete?
> Toggle panels: ajax-related attributes don't work
> -------------------------------------------------
>
> Key: RF-12839
> URL: https://issues.jboss.org/browse/RF-12839
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.1
> Environment: RichFaces 4.3.2-SNAPSHOT
> Metamer 4.3.2-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4
> JBoss AS 7.1.3.Final-redhat-4
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 25.0.1364.160 @ Linux x86_64
> Reporter: Pavol Pitonak
> Labels: regression
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # set oncomplete to "alert('complete')"
> # switch to tab 2 and back to tab 1
> result:
> * alert should be diplayed but isn't
> * tabs are correctly switched
> * worked fine in 4.2.3.Final
> * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status
> * affected components: tab, toggle panel item, accordion item
--
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, 3 months
[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes don't work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12839:
-------------------------------
Fix Version/s: 4.3.2
> Toggle panels: ajax-related attributes don't work
> -------------------------------------------------
>
> Key: RF-12839
> URL: https://issues.jboss.org/browse/RF-12839
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.1
> Environment: RichFaces 4.3.2-SNAPSHOT
> Metamer 4.3.2-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4
> JBoss AS 7.1.3.Final-redhat-4
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 25.0.1364.160 @ Linux x86_64
> Reporter: Pavol Pitonak
> Labels: regression
> Fix For: 4.3.2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # set oncomplete to "alert('complete')"
> # switch to tab 2 and back to tab 1
> result:
> * alert should be diplayed but isn't
> * tabs are correctly switched
> * worked fine in 4.2.3.Final
> * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status
> * affected components: tab, toggle panel item, accordion item
--
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, 3 months