mirror of
https://github.com/odoo/owl.git
synced 2025-10-06 19:59:41 +07:00
Géry Debongnie
398f9f4e53
From the beginning, Owl was designed to only call event handler on components that are mounted in the DOM. The main benefit is that if a component is destroyed, we are guaranteed to not execute any useless (or potentially dangerous code). However, there is one downside: if a component tree is being mounted, and a child component trigger an event in its mounted hook, then it cannot be caught by the parent, since the parent is technically not yet mounted. This may not be a good situation, but the point is that Owl unnecessarily prevent the handler to be called. We can fix this issue by simply checking if the component is not destroyed instead of checking that it is mounted. closes #809
🦉 OWL Documentation 🦉
Learning Owl
Are you new to Owl? This is the place to start!
- Tutorial: create a TodoList application
- Quick Overview
- How to start an Owl project
- How to test Components
- How to write Single File Components
- How to write debug Owl applications
Reference
You will find here a complete reference of every feature, class or object provided by Owl.
- Animations
- Browser
- Component
- Content
- Concurrency Model
- Configuration
- Context
- Environment
- Event Bus
- Event Handling
- Error Handling
- Hooks
- Mounting a component
- Miscellaneous Components
- Observer
- Props
- Props Validation
- QWeb Templating Language
- QWeb Engine
- Router
- Store
- Slots
- Tags
- Utils
Other Topics
This section provides miscellaneous document that explains some topics which cannot be considered either a tutorial, or reference documentation.
- Owl architecture: the Virtual DOM
- Owl architecture: the rendering pipeline
- Comparison with React/Vue
- Why did Odoo built Owl?
Found an issue in the documentation? A broken link? Some outdated information? Please open an issue or submit a PR!