Panel problem in easyui_html/css_WEB-ITnose
easyui interface panel scalable panel defaults
I have been using easyui to write the backend interface during this period, and I encountered a lot of problems. I looked at the documentation and asked Teacher Gu. Basically it’s okay, but it’s not. It's ideal. I have a question first. I hope someone can help me. It's how to make the panel (scalable panel) to be fully closed by default. Clicking on the corresponding node will open it.ps: I used 2 One panel is open by default and the other is not open by default.
Please reply...
Reply to the discussion (solution)
No one replied? Really not? Yes,
There is a shutdown attribute in the API. .
Under JS control, it can be directly set to closed when it is defined -
There is a closed attribute in the API. .
Under JS control, can it be set to closed directly when defining it? -
Is there? It seems not? I have tried it, and the default one is the first one to open. How to set it to close in js What?
$("#id").panel("close") No? Remember there is a close attribute. Look for it on the API.
$("#id").panel("close") doesn't work? Remember there is a close attribute and look for it on the api
EN It seems ok, thank you,

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The article discusses the HTML <datalist> element, which enhances forms by providing autocomplete suggestions, improving user experience and reducing errors.Character count: 159

The article discusses the HTML <progress> element, its purpose, styling, and differences from the <meter> element. The main focus is on using <progress> for task completion and <meter> for stati

The article discusses using HTML5 form validation attributes like required, pattern, min, max, and length limits to validate user input directly in the browser.

The article discusses the <iframe> tag's purpose in embedding external content into webpages, its common uses, security risks, and alternatives like object tags and APIs.

The article discusses the HTML <meter> element, used for displaying scalar or fractional values within a range, and its common applications in web development. It differentiates <meter> from <progress> and ex

Article discusses best practices for ensuring HTML5 cross-browser compatibility, focusing on feature detection, progressive enhancement, and testing methods.

The article discusses the viewport meta tag, essential for responsive web design on mobile devices. It explains how proper use ensures optimal content scaling and user interaction, while misuse can lead to design and accessibility issues.

This article explains the HTML5 <time> element for semantic date/time representation. It emphasizes the importance of the datetime attribute for machine readability (ISO 8601 format) alongside human-readable text, boosting accessibilit
