Styles C1Menu from 2010v1 to 2025v2 399

Styles C1Menu from 2010v1 to 2025v2 399

Posted by: enrique.pv-ext on 27 January 2026, 5:19 am EST

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 27 January 2026, 5:19 am EST - Updated 27 January 2026, 5:26 am EST

  Hi,

  Migrate from 2010v1 to 2025v2 399 in ASP.NET WebForms NET Framework 4.8.1.

  Using C1Menu from C1.Web.Wijmo.Controls.48.dll

  Change to new C1Menu control.

  		<cc1:C1Menu ID="C1Menu1" runat="server" Height="23px" OnLoad="C1Menu1_Load"
  			UseEmbeddedVisualStyles="False" VisualStyle="CustomVisualStyle"
  			VisualStylePath="~/VisualStyles" ClickToOpen="True" Width="295px"
  			ExpandDelay="0" CollapseDelay="0" CollapseDuration="250"
  			NestedGroupCheckable="False">
  			<Items>
  				<cc1:C1MenuItem runat="server" Text="Menú" NestedGroupCheckable="False">
  				</cc1:C1MenuItem>
  			</Items>
  		</cc1:C1Menu>

  2010 version:
  
  

  

  869×542 61.8 KB

  
  
  2025v2 399 version:
  
  

  

  572×688 67.3 KB

  
  
  problems with styles and CSS: align icon >, menuitem text width , …
  
  any suggestions ?

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 28 January 2026, 12:00 pm EST

  Hello,

  We have escalated your concerns to the development team for further insights [Internal Tracking ID: C1WEB-30307]

  Rest assured, we’ll get back once we have more information.

  Regards,
  
  Uttkarsh.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 23 April 2026, 8:33 am EST

  Hello Enrique,

  The team provided the following update:

  In the current 2025v2 (399) C1Menu, the styling model has fundamentally changed. The legacy properties such as UseEmbeddedVisualStyles, VisualStyle, and VisualStylePath are no longer supported. The control is now fully CSS-based, and its rendering structure differs from the 2010v1 implementation. Therefore, visual differences (item width behavior, icon alignment, submenu arrow positioning, etc.) are expected due to design changes in the newer control.

  Based on our review, the reported behavior appears to be a limitation or intentional architectural change in the current control rather than a defect.
  
  If achieving a UI identical to 2010v1 is required, this would need to be handled through custom CSS adjustments on the client side.

  • Rendering Model Changed

    In 2025v2, the server emits a minimal ul structure, and the jQuery c1menu widget dynamically transforms it at runtime. This differs from the older 2010v1 rendering model, which affects how CSS must target elements.

  • Legacy VisualStyle Properties Removed

    UseEmbeddedVisualStyles, VisualStyle, and VisualStylePath are no longer supported. Styling must now be handled via explicit theme CSS references and custom CSS overrides.

  • Width and Alignment Issues Root Cause

    • Default menu width is 150px unless overridden via the Width property or CSS targeting .wijmo-wijmenu.
    • The link element inside each item is styled at 92% width in the default CSS, which prevents the submenu arrow from aligning fully to the right.
    • Bootstrap theme CSS may introduce position: relative; left: 2px; on .ui-icon, which can interfere with arrow positioning.
    • Float-based layout in the default theme can cause misalignment of icons and text.

  • Recommended Approach

    • Reference the appropriate Wijmo theme CSS directly.
    • Set menu width using the control Width property or override .wijmo-wijmenu.
    • Replace float-based layout with display: flex on .wijmo-wijmenu-link for proper icon and arrow alignment.
    • Ensure correct CSS selectors are used (e.g., .wijmo-wijmenu-item, not .wijmo-mijmenu-item).

  Regards,
  
  Uttkarsh.