bevyengine / bevyengine/bevy

Clarify the Bevy UI and Taffy boundary

Open
#22,149 0 comments 0 reactions 0 assignees View on GitHub
A-UI C-Docs S-Ready-For-Implementation
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

## How can Bevy's documentation be improved?

There are several Bevy UI features that users naturally assume are handled by Taffy, such as:
* Responsive coords
* Border radius
* Z-Index
* Overflow clipping
* Outlines

But all of these are resolved internally in Bevy, either before or after the Taffy layout pass in `ui_layout_system`.

To make Bevy UI easier to understand for both users and contributors, the module's documentation should clearly explain which responsibilities belong to Taffy and which are handled by Bevy itself.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.