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

Remove block-progression from NZ and BO flags #788

Merged
merged 1 commit into from
Feb 5, 2021

Conversation

jorgemoya
Copy link
Contributor

@jorgemoya jorgemoya commented Jan 8, 2021

What

Prefix block-progression to -ms-block-progression.

Why

I don't know much about this property but seems to be deprecated or only used on old IE version. (source, source). I'm using the SVGs inside React + Typescript and I get a type error because block-progression needs to be prefixed by -ms-block-progression.

I don't even know if we need to keep it, maybe we can remove?

@NotTsunami
Copy link
Collaborator

NotTsunami commented Jan 19, 2021

You might want to switch to writing-mode instead since that seems to be the official standard and supercedes block-progression.

At the same time, w3schools suggests writing-mode is defaulted to horizontal-tb which is the setting we use. You should be able to fully remove this as it matches the default.

@jorgemoya
Copy link
Contributor Author

I will remove the values then.

@jorgemoya jorgemoya force-pushed the fix-blockprogression-nz branch from ac4f3f4 to 1e96400 Compare January 19, 2021 16:11
@jorgemoya jorgemoya changed the title Prefix block-progression on NZ and BO flags Remove block-progression on NZ and BO flags Jan 19, 2021
@jorgemoya jorgemoya changed the title Remove block-progression on NZ and BO flags Remove block-progression from NZ and BO flags Jan 19, 2021
@jorgemoya
Copy link
Contributor Author

@lipis Was wondering if there's any feedback for this and my other PR?

@lipis lipis merged commit f4bde1e into lipis:master Feb 5, 2021
@lipis
Copy link
Owner

lipis commented Feb 5, 2021

Sounds good!

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