Skip to content

remove some popper arrow styles and target tippy-arrow#268

Merged
RobbieTheWagner merged 4 commits intomasterfrom
bug/267
Oct 11, 2018
Merged

remove some popper arrow styles and target tippy-arrow#268
RobbieTheWagner merged 4 commits intomasterfrom
bug/267

Conversation

@chuckcarpenter
Copy link
Copy Markdown
Member

Fixes #266

Copy link
Copy Markdown
Contributor

@BrianSipple BrianSipple left a comment

Choose a reason for hiding this comment

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

This all LGTM, @chuckcarpenter. I thinking changing our approach to theming is something we can tackle in 3.0 -- perhaps just starting by leveraging Tippy's themes directly.

`
],
attachTo: '.hero-welcome bottom',
attachTo: '.hero-welcome bottom-start',
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@chuckcarpenter I'm seeing a few issues in the demo app:

screen shot 2018-10-10 at 2 16 09 pm

Did you mean to add the -start here?

Copy link
Copy Markdown
Contributor

@BrianSipple BrianSipple Oct 10, 2018

Choose a reason for hiding this comment

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

Also, I think we still need to add positioning calculations for -start and -end.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We've got a few styling issues here. I agree with @BrianSipple that we need to remove where we are creating popper arrows. We need to remove the borders/drop shadows from the arrows here as well.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@chuckcarpenter @rwwagner90 Perhaps it would be best to simply add to our existing Popper arrow styles for now (i.e., adding calculations for the -start and -end positions).

We could make fully converting to Tippy arrows a part of 2.X or 3.0.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@BrianSipple I'm okay with either, but it might be simpler to fully convert to tippy arrows now, rather than trying to use the old styles. I'll leave it up to you guys 😃

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@BrianSipple I think this is easier than adding the additional calculations though? This is a setting and falls back to Tippy options.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Adding the additional calculations would mean we don't risk breaking things like the positioning of the main content and aesthetic appearance of the arrows. Ultimately, using Tippy directly would be cleaner, but I feel like we'd be better off focusing on that after shipping 2.0.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@chuckcarpenter @rwwagner90 Setting the position to bottom-start still produces the screenshot above.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@chuckcarpenter @rwwagner90 This could be what we want, though. I was thinking the placement should move the arrow, but after revisiting both the Tippy and Popper demos, it appears that the main idea is to move the body of the tooltip.

Copy link
Copy Markdown
Contributor

@BrianSipple BrianSipple left a comment

Choose a reason for hiding this comment

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

If we're no longer using it, we should probably remove the part of our code that's creating a popper arrow

@chuckcarpenter
Copy link
Copy Markdown
Member Author

@BrianSipple Ch ch changes...

Copy link
Copy Markdown
Member

@RobbieTheWagner RobbieTheWagner left a comment

Choose a reason for hiding this comment

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

This seems more or less okay to me. We still need to clean up the theming and arrows at some point, but if this is good with you guys, it's good with me 👍

@BrianSipple
Copy link
Copy Markdown
Contributor

BrianSipple commented Oct 11, 2018

I'm good with this if I'm right that I was wrong here

@RobbieTheWagner
Copy link
Copy Markdown
Member

@BrianSipple your link isn't linking to what you were wrong about for me. Can you elaborate? If you and @chuckcarpenter agree that this is ready, one of you can feel free to merge. We should quickly follow up with extensive arrow and theming refactors though, probably.

@BrianSipple
Copy link
Copy Markdown
Contributor

BrianSipple commented Oct 11, 2018

@rwwagner90 It's the discussion where I requested changes. I thought that the styling of the tooltip was an issue -- but maybe it's not.

#268 (comment)

@RobbieTheWagner
Copy link
Copy Markdown
Member

@BrianSipple yeah that link still doesn't work. Perhaps a bug in GitHub, but it doesn't show the comment.

@BrianSipple @chuckcarpenter Just to reiterate, if you guys both agree this is good to go, feel free to merge. I just want to make sure that immediately after this we switch to using tippy arrows and themes directly, instead of doing a bunch of custom styles.

@chuckcarpenter
Copy link
Copy Markdown
Member Author

I think it's ready, then we can iterate further. Do you agree @BrianSipple ?

@RobbieTheWagner RobbieTheWagner merged commit f377171 into master Oct 11, 2018
@RobbieTheWagner RobbieTheWagner deleted the bug/267 branch October 11, 2018 15:04
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