JBoss Community Archive (Read Only)

GateIn Portal 3.8

Known Issues and Limitations

This is a new site and may have some issues which we have not foreseen or expected. If any issues are encountered please do not hesitate to file an issue under the mobile component or ask a question in the user forums. We highly value your feedback on how to improve the mobile experience.

Known Issues

Limitations

Administration Functionality and Portlets On Mobile Devices

The responsive site is mainly meant to be used by non-administrator users and support for administration functions may be limited on touch and smaller screened devices such as a phone.

  • GTNPORTAL-3060: Support Node Management on Mobile Devices Node Management on iOS based devices will currently not work due to mobile safari not supporting custom context menus. Some android browsers do support context menus by utilizing a long click and node management on these browsers do function correctly.

Container Layouts and Page Configurations

The webui containers and layouts were not designed to be mobile friendly. As such they cannot be really used to create responsive sites except for the 'Row Page Layouts' and the 'Row Layout Containers'. It is recommended to use only the row layouts for responsive portlets and to not specify the width or height of the containers or portlets. The row layouts will give your portlets the full width of the page and allows the portlet to handle how it should be rendered based on the browser's width.

If you want more complex layouts, such as column or mixed layouts, these will have to be done within the constraints of a single portlet and not through multiple portlets.

Group and User Sites

Group and user sites are shared between the various portal sites. There is currently no mechanism to customize or configure these sites to perform in one manner for the mobile site and another manner for the classic site. The only thing which changes is that the skin for these sites is set to the skin of the portal site which accesses it. As such, these sites cannot be properly configured to work with the mobile site without affecting how the classic site interacts with it. While on the group and user sites, the shared layout/user bar portlets will be displayed to allow the user to navigate from one area to another.

In the future the shared layout portlets may be modified in a way so that they can be reused for both the responsive site and the classic site.

The shared layout/user bar portlets are not optimal for mobile or touch based devices but they do work in a slightly limited manner. When navigation a menu, clicking once on a menu element will open the submenu for the element and clicking again will follow the link for the menu. While not idea, this should support the same functionality.

Using the Responsive Skin on the Classic Site or the Classic Skin on the Responsive Site

The responsive skin has been designed for the responsive/mobile site and the classic skin has been designed for the mobile site. It is recommended to use the skin on the site it was designed for, using the skin on another site may result in some minor graphical issues or inconsistencies. It may be recommended to remove the ability for users to specify their skin preferences.

JBoss.org Content Archive (Read Only), exported from JBoss Community Documentation Editor at 2020-03-10 13:22:38 UTC, last content change 2013-05-30 19:19:00 UTC.