Skip to content

Refine Tutorial positioning and fix mobile width constraint#17

Draft
google-labs-jules[bot] wants to merge 2 commits intomainfrom
tutorial-positioning-fix-9664505019768821353
Draft

Refine Tutorial positioning and fix mobile width constraint#17
google-labs-jules[bot] wants to merge 2 commits intomainfrom
tutorial-positioning-fix-9664505019768821353

Conversation

@google-labs-jules
Copy link
Contributor

This change fixes a critical issue in the Tutorial component where duplicate code was causing potential errors and implements a requested mobile-responsive width constraint. It removes a redundant useLayoutEffect block that referenced an undefined function and updates the tooltip's inline styles to safely handle small screens using standard CSS min() and calc() functions. The "Center Priority" positioning logic and "Smart Anti-shake" behavior via ResizeObserver are verified and preserved.


PR created automatically by Jules for task 9664505019768821353 started by @OsakaLOOP

- Remove duplicate and broken positioning code block in `src/components/Tutorial.jsx`.
- Implement robust `maxWidth` constraint for mobile devices using `min(24rem, calc(100vw - 40px))`.
- Ensure strict boundary clamping and center-priority positioning are preserved.
@google-labs-jules
Copy link
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Moved `handleNext` and `handleSkip` function definitions to the top of the component body, ensuring they are declared before being accessed by `useEffect` hooks. This resolves the 'handleNext accessed before declared' runtime error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants