[JBoss JIRA] (GTNPC-109) Modify EventResponse Interface to preserve window state changes accross multiple event invocations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPC-109?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on GTNPC-109:
-----------------------------------------------
Adam Kovari <akovari(a)redhat.com> made a comment on [bug 997036|https://bugzilla.redhat.com/show_bug.cgi?id=997036]
Description of problem:
Inclusion of https://issues.jboss.org/browse/GTNPC-109 in the future version of JPP 6
Version-Release number of selected component (if applicable):
JPP 6.0.0
> Modify EventResponse Interface to preserve window state changes accross multiple event invocations
> --------------------------------------------------------------------------------------------------
>
> Key: GTNPC-109
> URL: https://issues.jboss.org/browse/GTNPC-109
> Project: GateIn Portlet Container
> Issue Type: Enhancement
> Components: API
> Affects Versions: 2.4.1.Final
> Reporter: Adam Kovari
> Priority: Minor
> Fix For: 2.4.3.Final
>
> Attachments: 00905214-src.zip
>
>
> If a portlet changes it's window state in the event processing phase, this state is not preserved as other portlets/events can be processed on the same page and then portal will override this changes.
> The spec says:
> PLT.12.4 EventResponse Interface
> ================================
> The EventResponse interface extends the StateAwareResponse interface and adds the additional method setRenderParameters(EventRequest request). One thing to note is that if a portlet receives multiple processEvent calls while processing one client request the new portlet mode or window state that the portlet may have set, may be not validated by the portal between these multiple processEvent calls. This means that even if the portlet container may not throw an exception when the portlet sets a new portlet mode or window state that the portal may still not approve this portlet mode or window state change and call the portlet render method with a different portlet mode or window state.
> So the window state change can be preserved even accross multiple events invocation. Seems to be fine by the spec as shown above.
--
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] (GTNPC-109) Modify EventResponse Interface to preserve window state changes accross multiple event invocations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPC-109?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated GTNPC-109:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=997033
> Modify EventResponse Interface to preserve window state changes accross multiple event invocations
> --------------------------------------------------------------------------------------------------
>
> Key: GTNPC-109
> URL: https://issues.jboss.org/browse/GTNPC-109
> Project: GateIn Portlet Container
> Issue Type: Enhancement
> Components: API
> Affects Versions: 2.4.1.Final
> Reporter: Adam Kovari
> Priority: Minor
> Fix For: 2.4.3.Final
>
> Attachments: 00905214-src.zip
>
>
> If a portlet changes it's window state in the event processing phase, this state is not preserved as other portlets/events can be processed on the same page and then portal will override this changes.
> The spec says:
> PLT.12.4 EventResponse Interface
> ================================
> The EventResponse interface extends the StateAwareResponse interface and adds the additional method setRenderParameters(EventRequest request). One thing to note is that if a portlet receives multiple processEvent calls while processing one client request the new portlet mode or window state that the portlet may have set, may be not validated by the portal between these multiple processEvent calls. This means that even if the portlet container may not throw an exception when the portlet sets a new portlet mode or window state that the portal may still not approve this portlet mode or window state change and call the portlet render method with a different portlet mode or window state.
> So the window state change can be preserved even accross multiple events invocation. Seems to be fine by the spec as shown above.
--
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] (GTNPORTAL-3239) GateIn Redirect Admin UI: Alert shows <undefined><undefined> if shown when previous is fading
by Alexandre Mendonça (JIRA)
Alexandre Mendonça created GTNPORTAL-3239:
---------------------------------------------
Summary: GateIn Redirect Admin UI: Alert shows <undefined><undefined> if shown when previous is fading
Key: GTNPORTAL-3239
URL: https://issues.jboss.org/browse/GTNPORTAL-3239
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.6.1.Final
Reporter: Alexandre Mendonça
Assignee: Alexandre Mendonça
If two actions which show alert notification (eg: delete and save redirect) are done in such short time so that the 2nd alert comes in when the 1st is fading out, the alert is show as "<undefined> <undefined>" and in yellow (default) color.
--
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] (GTNPORTAL-2940) XSS attack on Display Name of registration form
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2940?page=com.atlassian.jira.pl... ]
Trong Tran resolved GTNPORTAL-2940.
-----------------------------------
Assignee: Trong Tran (was: Hai Nguyen)
Fix Version/s: 3.7.0.Final
Resolution: Done
> XSS attack on Display Name of registration form
> -----------------------------------------------
>
> Key: GTNPORTAL-2940
> URL: https://issues.jboss.org/browse/GTNPORTAL-2940
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Hai Nguyen
> Assignee: Trong Tran
> Labels: done, portal-s70
> Fix For: 3.7.0.Final
>
>
> When Display Name of an user contains script, it's executed when going to Dashboard. (logo portlet contains user's display name)
> Steps to check:
> * Register new user with display name is "<script>alert('test')</script>"
> * Login as new user
> * Go to Dashboard
> Problem: alert popup is shown.
--
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, 5 months