-
ABP Framework version: v7.2.2
-
UI type: Angular
-
DB provider: EF Core
-
Tiered (MVC) or Identity Server Separated (Angular): yes
When LeptonX enters the mobile view it renders icons for the first and last 2 menu items with the remainder in the hamburger menu. However if the 2nd menu item contains sub-menus they do not open. The settings menu does open correctly.
This problem can be seen on the LeptonX demo site: https://x.leptontheme.com/side-menu/# when viewed on mobile the 'Components' menu does not open when clicked/touched. The expected behavior is that the menu opens in the same way as the settings menu.
My project is build on microservice template, the 2nd menu is generated by ABP Suite from one of my services and shows the same issue.
2 Answer(s)
-
0
Hi There,
Please see package.json:{ "name": "CloudBiz", "version": "0.0.0", "scripts": { "ng": "ng", "start": "ng serve --open", "build": "ng build", "build:prod": "ng build product --configuration production && ng build CloudBiz --configuration production ", "watch": "ng build --watch --configuration development", "test": "ng test", "lint": "ng lint" }, "private": true, "dependencies": { "@abp/ng.components": "~7.2.2", "@abp/ng.core": "~7.2.2", "@abp/ng.oauth": "~7.2.2", "@abp/ng.setting-management": "~7.2.2", "@abp/ng.theme.shared": "~7.2.2", "@angular/animations": "^15.0.4", "@angular/common": "^15.0.4", "@angular/compiler": "^15.0.4", "@angular/core": "^15.0.4", "@angular/forms": "^15.0.4", "@angular/localize": "^15.0.4", "@angular/platform-browser": "^15.0.4", "@angular/platform-browser-dynamic": "^15.0.4", "@angular/router": "^15.0.4", "@volo/abp.commercial.ng.ui": "~7.2.2", "@volo/abp.ng.account": "~7.2.2", "@volo/abp.ng.audit-logging": "~7.2.2", "@volo/abp.ng.identity": "~7.2.2", "@volo/abp.ng.openiddictpro": "~7.2.2", "@volo/abp.ng.language-management": "~7.2.2", "@volo/abp.ng.saas": "~7.2.2", "@volo/abp.ng.text-template-management": "~7.2.2", "@volosoft/abp.ng.theme.lepton-x": "^2.0.0", "rxjs": "7.5.6", "tslib": "^2.1.0", "zone.js": "~0.11.4", "apexcharts": "^3.39.0", "ng-apexcharts": "^1.7.5" }, "devDependencies": { "@abp/ng.schematics": "~7.2.2", "@angular-devkit/build-angular": "^15.0.4", "@angular-eslint/builder": "~15.1.0", "@angular-eslint/eslint-plugin": "~15.1.0", "@angular-eslint/eslint-plugin-template": "~15.1.0", "@angular-eslint/schematics": "~15.1.0", "@angular-eslint/template-parser": "~15.1.0", "@angular/cli": "^15.0.4", "@angular/compiler-cli": "^15.0.4", "@angular/language-service": "^15.0.4", "@types/jasmine": "~3.6.0", "@types/node": "^12.11.1", "@typescript-eslint/eslint-plugin": "^5.43.0", "@typescript-eslint/parser": "^5.43.0", "eslint": "^8.28.0", "jasmine-core": "~4.0.0", "karma": "~6.3.0", "karma-chrome-launcher": "~3.1.0", "karma-coverage": "~2.1.0", "karma-jasmine": "~4.0.0", "karma-jasmine-html-reporter": "^1.7.0", "ng-packagr": "^15.0.3", "typescript": "~4.8.3" } } -
0
Hi ash, I created an issue for that, It'll be fixed on next patch version
