Skip to content

Conversation

@jamesnw
Copy link
Collaborator

@jamesnw jamesnw commented Sep 24, 2025

Run npx http-server .
Open http://localhost:8080/src/dropdown

@dvdherron
Copy link

@jamesnw I have some style cleanup edits I thought would be easier to do locally. Could you grant me access here?

@jamesnw
Copy link
Collaborator Author

jamesnw commented Sep 25, 2025

@dvdherron Whoops, sorry- you should have access now!

@dvdherron dvdherron requested a review from stacyk September 25, 2025 20:14
@dvdherron
Copy link

@stacyk This is ready for style review whenever you're ready

@netlify
Copy link

netlify bot commented Oct 17, 2025

Deploy Preview for oddbaseline ready!

Name Link
🔨 Latest commit 6f85fc2
🔍 Latest deploy log https://app.netlify.com/projects/oddbaseline/deploys/690caa6dbf76ce0008275131
😎 Deploy Preview https://deploy-preview-1--oddbaseline.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dvdherron dvdherron self-requested a review October 23, 2025 14:45
@dvdherron
Copy link

@jamesnw The entry and exit transitions are working fine on the outer popover. Haven't figured out yet why the exit animation isn't working on the nested popovers though.

Copy link
Collaborator Author

@jamesnw jamesnw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Safari, the menus are filling the height of the containing block. Not sure what's going on there.

Image

It looks like the li is flex, and the <ul popover> is seen as a flex item, so it's taking up space.

opacity var(--slow),
inset var(--fast),
overlay var(--slow) allow-discrete,
display var(--slow) allow-discrete;
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wasn't there an issue with allow-discrete and Firefox on the CQ demo? Does that apply here as well?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, but I'm not seeing the exit animation in Chrome either. Anything obvious sticking out to you @stacyk?

const formerLink = document.querySelector("[aria-current]");
if (formerLink) formerLink.removeAttribute("aria-current");

const linkToRoute = document.querySelector(`[href="${newPage}"]`);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what's happening, but this line seems to be crashing in Safari. I'll look into this more.

@dvdherron
Copy link

It looks like the li is flex, and the <ul popover> is seen as a flex item, so it's taking up space.

Seems like Safari requires align-content start here. I think I cleaned that up here: d3ce6fa

@jamesnw
Copy link
Collaborator Author

jamesnw commented Oct 27, 2025

It looks like the li is flex, and the <ul popover> is seen as a flex item, so it's taking up space.

Seems like Safari requires align-content start here. I think I cleaned that up here: d3ce6fa

This is defined on :popover-open so it reverts to the old view during the close animation. Should it be on [data-menu]?

position-try-fallbacks: flip-inline;
inline-size: max-content;
min-inline-size: anchor-size();
inset-block-start: var(--outer-popover-inset, var(--popover-offset));
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The inset here and in nested seems to be breaking Safari somehow? Is it actually needed?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking into this, but it's what we're using to slide the outer popovers down and the nested popovers horizontally. I'll see if there's a fix or if it can be done a different way.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don’t do too much with this yet- I’d like to figure out why this is breaking Safari first

@dvdherron
Copy link

It looks like the li is flex, and the <ul popover> is seen as a flex item, so it's taking up space.

Seems like Safari requires align-content start here. I think I cleaned that up here: d3ce6fa

This is defined on :popover-open so it reverts to the old view during the close animation. Should it be on [data-menu]?

does this fix it? 5818b8f

I have only tested on an older version of Safari on Saucelabs and it looks fine there.

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.

3 participants