//! Hit-testing logic for layout windows

//!

//! This module handles determining which DOM nodes are under the mouse cursor

//! and resolving the cursor icon based on CSS cursor properties.

//!

//! ## Cursor Resolution Algorithm

//!

//! WebRender returns hit-test results in **front-to-back** order:

//! - `depth = 0` is the frontmost/topmost element (closest to the user)

//! - Higher depth values are further back in the z-order

//!

//! The algorithm finds the **frontmost** node that has an explicit CSS `cursor`

//! property set. If no node has a cursor property, we check if the node has

//! text children and use their cursor property (typically `cursor:text`).

//!

//! ## Design Principles

//!

//! 1. **Frontmost priority**: The node closest to the user (lowest depth) takes

//!    precedence. This matches browser behavior where a button's cursor:pointer

//!    overrides any parent's cursor setting.

//!

//! 2. **Text-child inheritance**: Text nodes are inline and don't get hit-test areas.

//!    Their container inherits the text node's cursor if the container has no explicit

//!    cursor property. This shows I-beam cursor over text containers.

//!

//! 3. **Explicit cursor wins**: If a container has an explicit cursor property

//!    (like `cursor:pointer` on a button), it overrides any text-child cursor.

// Re-export FullHitTest for use by other layout modules

pub use azul_core::hit_test::FullHitTest;

use azul_core::{

    dom::{DomId, DomNodeId, NodeId},

    hit_test::{HitTest, HitTestItem},

    window::MouseCursorType,

};

use azul_css::props::style::StyleCursor;

use crate::window::LayoutWindow;

/// Result of cursor type hit-testing, determines which mouse cursor to display

#[derive(Debug, Clone, Default, PartialEq)]

pub struct CursorTypeHitTest {

    /// The node that has a non-default cursor property (if any)

    pub cursor_node: Option<(DomId, NodeId)>,

    /// The mouse cursor type to display

    pub cursor_icon: MouseCursorType,

}

impl CursorTypeHitTest {

    /// Create a new cursor type hit-test from a full hit-test and layout window.

    ///

    /// Finds the frontmost (lowest depth) node with a cursor property by checking

    /// cursor_hit_test_nodes (text runs) and regular_hit_test_nodes (DOM nodes).

        use azul_core::hit_test_tag::CursorType;

        // Start with MAX so any node with a cursor property will be selected

        // Iterate through all hovered nodes across all DOMs

            // Get the layout result for this DOM

            };

            // Check cursor_hit_test_nodes (direct text run hits with cursor

            // type encoded in the tag, no CSS lookup needed)

                // Only consider if it's in front of our current best

                // Convert CursorType to MouseCursorType

                // Only use this cursor if it's not the default

                // (allows containers behind text to show their cursor if text has default)

            }

            // Check regular_hit_test_nodes (DOM nodes with CSS cursor property)

                // Only consider this node if it's in front of our current best

                // CHECKED access: hit-test results can reference a PREVIOUS

                // generation of a VirtualView child DOM — the child is rebuilt

                // in place with fresh (possibly fewer) NodeIds while the hover

                // state / CPU hit-tester still hold last frame's ids (e.g.

                // panning the MapWidget shrinks the tile grid). Blind indexing

                // panicked here ("len is 25 but the index is 27"); a stale id is

                // skipped instead — the next pointer move re-hit-tests against

                // the fresh tree.

                ) else {

                };

                // Query the CSS cursor property for this node

                );

                // If this node has an explicit cursor property, use it

                    // No explicit `cursor`: editable text (contenteditable / a

                    // <textarea>) defaults to the I-beam, like browsers — so a

                    // multi-line textarea shows the text cursor on hover even

                    // without `cursor: text` in CSS. (A single-line input already

                    // gets the I-beam from its text-run cursor tag / explicit CSS;

                    // this makes them consistent. Does NOT affect the text_input

                    // widget, which sets cursor:text explicitly and so takes the

                    // branch above.)

                }

            }

        }

}

/// Translate CursorType (from hit-test tag) to MouseCursorType

    use azul_core::hit_test_tag::CursorType;

    }

/// Translate CSS cursor value to MouseCursorType

    use azul_css::props::style::effects::StyleCursor;

    }

#[cfg(test)]

mod tests {

    use super::*;

    use azul_core::dom::DomNodeId;

    use azul_core::dom::OptionDomNodeId;

    #[test]

    #[test]

            hit_test.focused_node,

        );

    #[test]

    #[test]

        use azul_css::props::style::effects::StyleCursor;

            MouseCursorType::Default

        );

            MouseCursorType::Hand

        );

            MouseCursorType::Crosshair

        );

}