December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12447) Editor: color picking doesn't work in Internet Explorer 10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12447?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12447: ------------------------------- Sprint: 4.3.0.CR1 - Bug fixes > Editor: color picking doesn't work in Internet Explorer 10 > ---------------------------------------------------------- > > Key: RF-12447 > URL: https://issues.jboss.org/browse/RF-12447 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final, 4.3.0.M1 > Environment: RichFaces 4.2.2.Final, 4.3.0.M1 > Internet Explorer 10 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Attachments: editor-ie10.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > # open Showcase http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=editor&... > # open developers tools and change document mode to "Standards" > # try to change color of title > result: > * popup for color chooser is misplaced > * when a color is selected, nothing happens > * there are JavaScript errors in the console > * works fine when document mode is set to "IE8 standards" -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12678: ------------------------------- Sprint: 4.3.0.CR1 - Bug fixes > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Priority: Minor > Labels: regression > Fix For: 4.3.0.CR1 > > Attachments: editorJSerror1.png, editorJSerror2.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- 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

1
0
0 / 0

[JBoss JIRA] (RF-11565) Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11565?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11565: ------------------------------- Sprint: 4.3.0.CR1 - Bug fixes > Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used > --------------------------------------------------------------------------------------- > > Key: RF-11565 > URL: https://issues.jboss.org/browse/RF-11565 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Milestone3, 4.2.3.CR1, 4.3.0.M3 > Environment: iPhone 4 (Safari) > Nexus (Android 2.3.6) > Google Chrome 12.0.742.112 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The second a third autocomplete input in Showcase demo http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=autoco... [1] doesn't work properly on the mentioned browsers/devices: > # type "Al" > # select "Alabama" -> input field is containing "Alabama" > # type ", P" > # select "Pennsylvania" with mouse/finger -> input field is containing "Pennsylvania, P" (it should contain "Alabama, Pennsylvania") > The Safari developer's console on iPhone doesn't display any error. > It works properly on: > - Opera 11.50 > - Firefox 6.0 > [1] http://10.0.2.2:8080/showcase/#autocomplete:modes in movile showcase -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12679) onerror attribute is missing in fileUpload

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12679?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12679: ------------------------------- Fix Version/s: 5-Tracking > onerror attribute is missing in fileUpload > ------------------------------------------ > > Key: RF-12679 > URL: https://issues.jboss.org/browse/RF-12679 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final > Reporter: Siarhei Khamenka > Priority: Critical > Fix For: 5-Tracking > > > onerror attribute is missing from in:fileUpload in 4.2.2 -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12680) Infinite XHR after error on fileUpload

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12680?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12680: ------------------------------- Fix Version/s: 5-Tracking > Infinite XHR after error on fileUpload > -------------------------------------- > > Key: RF-12680 > URL: https://issues.jboss.org/browse/RF-12680 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final > Reporter: Siarhei Khamenka > Fix For: 5-Tracking > > Attachments: infinite-progress.png > > > After fileUpload failed due to HTTP error "413 Request Entity Too Large" progress bar sends infinite requests to server. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12678: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Priority: Minor > Labels: regression > Fix For: 4.3.0.CR1 > > Attachments: editorJSerror1.png, editorJSerror2.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12677) Showcase - deploying from eclipse - update docs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12677?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12677: ------------------------------- Fix Version/s: 4.3.0.CR1 > Showcase - deploying from eclipse - update docs > ----------------------------------------------- > > Key: RF-12677 > URL: https://issues.jboss.org/browse/RF-12677 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.M3 > Reporter: Juraj Húska > Priority: Minor > Fix For: 4.3.0.CR1 > > > I found deploying showcase from eclipse non trivial and IMHO it should be documented in docs somewhere. Good place is [readme.txt|https://github.com/richfaces/showcase/blob/develop/readme.txt] of showcase repository I think. > There is mentioned how to deploy from CLI and how to import showcase to eclipse but it misses info how to deploy from eclipse. > To deploy from eclipse on jboss as 7.1.x one needs to: > # set maven profile to {{jbas71}} > # alter deployment assembly to contains {{resources-jbas71}}, {{webapp-jbas71}}, {{wepapp}}, {{resources}} > # start container with {{standalone-full.xml}} configuration > # be aware of the fact that eclipse likes to add empty persistent.xml by default if it is there, so one need to check it and remove it > # eclipse tool ignores context root from jboss-web.xml, so it loads {{richfaces-showcase}} instead of correct showcase context root (I believe it is caused by JBIDE-473). > Feel free to ask me for pull request or reject it if you found it too much detailed for that [readme.txt|https://github.com/richfaces/showcase/blob/develop/readme.txt]. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12681) Curious settings for rf-cal-hov in calendar.ecss

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12681?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12681: ------------------------------- Description: CSS specification is redundant / inconsistent: {code} .rf-cal-hov { background-color: '#{richSkin.calendarSpecBackgroundColor}'; background-color: '#{richSkin.calendarSpecTextColor}'; } {code} Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . was: CSS specification is redundant / inconsistent: .rf-cal-hov { background-color: '#{richSkin.calendarSpecBackgroundColor}'; background-color: '#{richSkin.calendarSpecTextColor}'; } Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . > Curious settings for rf-cal-hov in calendar.ecss > ------------------------------------------------ > > Key: RF-12681 > URL: https://issues.jboss.org/browse/RF-12681 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final > Reporter: Lutz Ulrich > Priority: Trivial > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > CSS specification is redundant / inconsistent: > {code} > .rf-cal-hov { > background-color: '#{richSkin.calendarSpecBackgroundColor}'; > background-color: '#{richSkin.calendarSpecTextColor}'; > } > {code} > Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12681) Curious settings for rf-cal-hov in calendar.ecss

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12681?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12681: ------------------------------- Fix Version/s: 4.2.3.CR1 > Curious settings for rf-cal-hov in calendar.ecss > ------------------------------------------------ > > Key: RF-12681 > URL: https://issues.jboss.org/browse/RF-12681 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final > Reporter: Lutz Ulrich > Priority: Trivial > Fix For: 4.2.3.CR1 > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > CSS specification is redundant / inconsistent: > {code} > .rf-cal-hov { > background-color: '#{richSkin.calendarSpecBackgroundColor}'; > background-color: '#{richSkin.calendarSpecTextColor}'; > } > {code} > Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12675: ------------------------------- Fix Version/s: 5-Tracking > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Priority: Critical > Labels: Drag, drop, myfaces > Fix For: 5-Tracking > > Attachments: dragAndDrop.zip > > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2012