A-Frame raycaster visibility behavior needs diagnosis

A-Frame’s raycaster component supports scoped intersection testing through objects, interval, near, and far. One behavior remains unclear for review: whether an entity marked visible=false is excluded from intersections and from raycaster-intersected events.

The documentation does not consistently define that visibility rule across A-Frame 1.x and 2.0 pre-release versions. Because the component relies on three.js raycasting, the bundled three.js version may also affect traversal of invisible objects. The target A-Frame release and its dependency version therefore need to be identified before the behavior is classified as expected.

For the version under test, should an invisible entity ever receive raycaster-intersected? Does the objects selector alter that outcome, and what release-specific evidence or controlled comparison of otherwise identical visible and hidden entities would settle the rule?