-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.2.0 CE B1
-
Fix Version/s: 6.2.0 CE B1
-
Component/s: Portal Services, Portal Services > Mobile Device Rules
-
Labels:None
-
Epic/Theme:
-
Git Pull Request:
The use cases originally WAP was thought for are replaced by new features in current version (like mobile device rules & responsive design), so this doesn't make sense anymore. It is currently adding noise to the UI and it is not needed, as it can confuse the users.
This needs to be deprecated on 6.2 using a property that hides the appropriate options from the UI (see screenshots) but which can be enabled again in case a customer is still using this technology. This will be fully removed on next version.
The property should be called wap.styling.enabled and should set to false by default.
- causes
-
LPS-53842 In some parts, usage of WAP themes does not honor wap.styling.enabled/mobile.device.styling.wap.enabled
- Closed
-
LPS-37764 If mobile.device.styling.wap.enabled is false we should use regular
- Closed
-
LPS-38624 Portlets' Look and Feel configuration features are repetitive
- Closed
- is related to
-
LRDOCS-686 New method to differentiate regular browser and mobile themes
-
- Closed
-
- relates
-
LPS-37764 If mobile.device.styling.wap.enabled is false we should use regular
- Closed