[JBoss JIRA] (RF-13181) Autocomplete: suggestion list is not valid HTML code
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13181?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13181 at 10/7/13 3:57 PM:
----------------------------------------------------------
Fixed in upstream: https://github.com/richwidgets/richwidgets/issues/33
was (Author: lfryc):
Fixed in upstream:
> Autocomplete: suggestion list is not valid HTML code
> ----------------------------------------------------
>
> Key: RF-13181
> URL: https://issues.jboss.org/browse/RF-13181
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # check suggestion list's markup
> result:
> * Autocomplete generates an unsorted list (ul) with several list items (li), one for each suggestion. However, inside each li, there is yet another li which is not allowed by HTML.
> {code:xml}
> <ul class="ui-autocomplete ui-menu ui-widget ui-widget-content ui-corner-all" id="ui-id-1" tabindex="0" style="z-index: 1; display: block; top: 237.0142364501953px; left: 10px; width: 161px;">
> <li class="ui-menu-item" role="presentation">
> <a id="ui-id-7" class="ui-corner-all" tabindex="-1">
> <li>Alabama</li>
> </a>
> </li>
> ...
> </ul>
> {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
12 years, 3 months
[JBoss JIRA] (RF-13181) Autocomplete: suggestion list is not valid HTML code
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13181?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13181:
---------------------------------
Fixed in upstream:
> Autocomplete: suggestion list is not valid HTML code
> ----------------------------------------------------
>
> Key: RF-13181
> URL: https://issues.jboss.org/browse/RF-13181
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # check suggestion list's markup
> result:
> * Autocomplete generates an unsorted list (ul) with several list items (li), one for each suggestion. However, inside each li, there is yet another li which is not allowed by HTML.
> {code:xml}
> <ul class="ui-autocomplete ui-menu ui-widget ui-widget-content ui-corner-all" id="ui-id-1" tabindex="0" style="z-index: 1; display: block; top: 237.0142364501953px; left: 10px; width: 161px;">
> <li class="ui-menu-item" role="presentation">
> <a id="ui-id-7" class="ui-corner-all" tabindex="-1">
> <li>Alabama</li>
> </a>
> </li>
> ...
> </ul>
> {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
12 years, 3 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Milo van der Zee (JIRA)
Milo van der Zee created RF-13250:
-------------------------------------
Summary: Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
Key: RF-13250
URL: https://issues.jboss.org/browse/RF-13250
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.4
Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
Reporter: Milo van der Zee
Hello,
I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
I also started seeing this message lot's of times:
{{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
In the crashed system heap dump I see a lot of:
- AtomicBoolean (751.000, 15.0MB)
- ConcurrentLinkedQueue
- AtmospereRequest$Builder (60.042, 13.8MB)
To me it looks like it has something to do with Atmosphere. Any ideas?
Thanks,
Milo van der Zee
--
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
12 years, 3 months
[JBoss JIRA] (RF-13249) PushServlet initialized twice
by Milo van der Zee (JIRA)
Milo van der Zee created RF-13249:
-------------------------------------
Summary: PushServlet initialized twice
Key: RF-13249
URL: https://issues.jboss.org/browse/RF-13249
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.3.4
Reporter: Milo van der Zee
Priority: Minor
In PushServlet of Richfaces 4.3.4 I see there is a flag 'private boolean initialized = false;'. This is done to NOT initialize the servlet multiple times. But the servlet is also initialized to attach the Atmosphere handler. Idea of Lukáš Fryč is to break the init code appart. One to init the servlet and one to connect the Atmosphere handler.
Also see the forum thread
--
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
12 years, 3 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12802:
---------------------------------
*HotKey fragment - automatically retrieve the hotkey combination via JS*
I don't like that one, since it distracts the functional test from following an approach of testing interface contract.
If functional test suppose to verify that interface (in this case user interface) reacts as expected, then the tester really needs to hard-code a way how the function is performed. Otherwise the test won't guard against regressions caused by change of the application logic.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
12 years, 3 months
[JBoss JIRA] (RF-11413) Popup panel, component values on popup panel are not updated after validation process fails
by Frank Ruenagel (JIRA)
[ https://issues.jboss.org/browse/RF-11413?page=com.atlassian.jira.plugin.s... ]
Frank Ruenagel commented on RF-11413:
-------------------------------------
Helpful could be: https://community.jboss.org/message/840345#840345
> Popup panel, component values on popup panel are not updated after validation process fails
> -------------------------------------------------------------------------------------------
>
> Key: RF-11413
> URL: https://issues.jboss.org/browse/RF-11413
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core, component-input, component-validators, showcase
> Affects Versions: 4.0.0.Final
> Reporter: Eldin Okanovic
> Fix For: 5-Tracking
>
>
> Bug is on richfaces 4 showcase. (rich:datatable->table edit). The situation is next:
> i try to edit row on table, popup panel occurs. I enter a not valid value i.e. for price, and as it suppose to do validation message occurs. Then i close popup panel and try edit a different row, popup panel occurs with some fields correctly filled, and some are filled with old values.
> I think that component update process is not completed.
--
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
12 years, 3 months
[JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13248:
-------------------------------
Summary: Switch RichFaces smoke tests to run on WildFly 8 by default
Key: RF-13248
URL: https://issues.jboss.org/browse/RF-13248
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 5.0.0.Alpha2
Reporter: Lukáš Fryč
Fix For: 5.0.0.Alpha2
With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means:
* tweaking TravisCI configuration
Note that tests have problem to pass on WildFly Beta1:
{code}
Tests run: 34, Failures: 1, Errors: 16, Skipped: 1
{code}
so we need to analyze a cause of the failure first.
--
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
12 years, 3 months
[JBoss JIRA] (RF-13247) Richfaces 4.3.x not compatible with guava 15.0
by Jeremy Landis (JIRA)
Jeremy Landis created RF-13247:
----------------------------------
Summary: Richfaces 4.3.x not compatible with guava 15.0
Key: RF-13247
URL: https://issues.jboss.org/browse/RF-13247
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Jeremy Landis
Priority: Minor
Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue.
Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl
--
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
12 years, 3 months