Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FX-121] Add support for Safari with clip-path #150

Merged
merged 3 commits into from
Apr 5, 2019

Conversation

denieler
Copy link
Collaborator

@denieler denieler commented Apr 5, 2019

FX-121

Description

Add css prefix for clip-path to add Safari support

@denieler denieler requested a review from a team as a code owner April 5, 2019 11:41
@toptal-devbot
Copy link
Collaborator

Successfully deployed demo at https://picasso.toptal.net/fix-clip-path-support

@@ -36,7 +36,8 @@ export default ({ palette }: Theme) =>
fontSize: '4.5rem'
},
clippedCorner: {
clipPath: getClipPathCornerMask('0.3em')
clipPath: getClipPathCornerMask('0.3em'),
'-webkit-clip-path': getClipPathCornerMask('0.3em')
Copy link
Contributor

Choose a reason for hiding this comment

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

Strange, doesn't JSS has auto prefixing? Maybe we could enable it somehow in order to avoid such cases?

Copy link
Contributor

Choose a reason for hiding this comment

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

We already discussed that with daniel, I also believe we shouldn't do manual prefixing, so far I've found https://cssinjs.org/jss-plugin-vendor-prefixer but still it's more than strange .... I think MUI needs to have prefixing enabled and maybe we are just missing something ...

Copy link
Contributor

@vedrani vedrani Apr 5, 2019

Choose a reason for hiding this comment

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

Can we add that plugin to webpack config in storybook?

@MilosMosovsky
Copy link
Contributor

As daniel found out @vedrani @bytasv cssinjs/css-vendor#74 :D :D

@vedrani
Copy link
Contributor

vedrani commented Apr 5, 2019

Yes, I was just reading about it. Crazy

@denieler
Copy link
Collaborator Author

denieler commented Apr 5, 2019

That's just horrible in 2019... JSS

@toptal-devbot
Copy link
Collaborator

Successfully deployed demo at https://picasso.toptal.net/fix-clip-path-support

@denieler denieler added the Bugfix Something isn't working label Apr 5, 2019
@toptal-devbot
Copy link
Collaborator

Successfully deployed demo at https://picasso.toptal.net/fix-clip-path-support

Additional notes:
* The shape of clipped corner has a fallback for <=IE11, Edge to just a rectangle
`
)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add for this field also markdown support in storybook. Maybe not this PR but new ticket.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

we do have markdown support for the Description now :) or which one you mean?

Copy link
Contributor

@vedrani vedrani Apr 8, 2019

Choose a reason for hiding this comment

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

Ok, cool, but why do you need &nbsp;?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@vedrani this is the only one way to add new-line in this react-markdown :( and it's not just &nbsp;, but &nbsp; (with two spaces in the end)... I know.. but it works :) nothing else didn't what I've tried, like multiple enters, <br/>, , \r\n, none of them :(

@denieler denieler merged commit 0ac705c into master Apr 5, 2019
@denieler denieler deleted the fix-clip-path-support branch April 5, 2019 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugfix Something isn't working
Projects
None yet
5 participants