#324: unbury the scene-mode picker's expanded 2D/Columbus buttons#331
Merged
rdhyee merged 2 commits intoJul 11, 2026
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AjnkWb4HpuLeDbYfzmY3X9
…buttons Root cause of Andrea's "clicked the globe button, nothing happened": the custom vertical toolbar stacks the baseLayerPicker button directly below the sceneModePicker, and the picker's expanded 2D/Columbus buttons drop DOWN into that space — the later sibling paints on top and receives the clicks (reproduced on prod: elementFromPoint at the 2D button's center returns .cesium-baseLayerPicker-selected). Fix: give .cesium-sceneModePicker-wrapper a stacking context above its siblings (position: relative + z-index: 1100, matching the adjacent baseLayerPicker-dropDown rule's convention). Note: this restores Cesium's stock 2D/Columbus switching; "officially supported 2D" (testing the altitude-gated behaviors in 2D) remains the larger isamplesorg#324 conversation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AjnkWb4HpuLeDbYfzmY3X9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
The custom vertical toolbar stacks the base-layer picker directly below the scene-mode picker. Cesium expands the 2D/Columbus buttons downward — into the base-layer picker's space — and without a stacking context the later sibling paints on top and eats the clicks. Reproduced on production:
elementFromPointat the 2D button's center returned.cesium-baseLayerPicker-selected.Fix
.cesium-sceneModePicker-wrapper { position: relative; z-index: 1100; }— same convention as the adjacentbaseLayerPicker-dropDownrule.Verified (fork preview, fresh context)
Click globe button → dropdown expands → the element at the 2D button's center is now the button's own icon → click → the globe morphs to a flat 2D map (screenshot in #324 thread), picker then offers 3D to switch back. Zero console errors. Also incidentally demonstrates cluster rendering works in 2D at world zoom.
Note: this restores Cesium's stock mode switching; "officially supported 2D" (testing altitude-gated behaviors in 2D) remains the larger #324 conversation.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AjnkWb4HpuLeDbYfzmY3X9