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

Feature/autoprefixer #50

Merged
merged 7 commits into from
Mar 4, 2019
Merged

Feature/autoprefixer #50

merged 7 commits into from
Mar 4, 2019

Conversation

toddmilliken
Copy link
Contributor

Adds a new feature, autoprefixer, which was brought up in Foundation issue bu-ist/responsive-foundation#204 and executed in Foundation PR bu-ist/responsive-foundation#210. View those links for background on how autoprefixer can help our front-end workflow and establish concrete browser support for projects.

Changes

  • Adds autoprefixer with grunt-postcss package
  • Updates Gruntfile.js to apply Post CSS transforms on the compiled admin, ie, styles CSS files.

Companion PRs

Review checklist

@toddmilliken
Copy link
Contributor Author

toddmilliken commented Mar 4, 2019

Note: Code Climate issues for Unexpected trailing comma. in the Gruntfile.js file will go away once we upgrade our javascript workflow and have the new eslint configuration setup, which follows WP best practices. See existing PR #48

Copy link
Contributor

@ashleykolodziej ashleykolodziej left a comment

Choose a reason for hiding this comment

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

Looks good. Can you take care of the build task edit below and also add a note that with this release, there is a significant change to browser support out of the box, and a way to find out what browsers are supported? Some projects with older SOWs may want to start with a previous version of child starter for browser support reasons. Or, alternately, add some documentation for how to edit the browser support list.

Gruntfile.js Outdated Show resolved Hide resolved
Gruntfile.js Outdated
autoprefixer, // add vendor prefixes.
],
},
src: ['ie.css', 'ie.min.css', 'style.css', 'style.min.css'],
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we actually want to run postcss on IE stylesheets? They're only loaded on old versions of IE that support the conditional comment syntax.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

At first glace I figured I'd add it in, but this is a good point. After looking further into it, the IE stylesheets seem to be loaded in addition to the regular stylesheet, so the postcss transforms could increase filesize.

ashleykolodziej and others added 2 commits March 4, 2019 11:20
Co-Authored-By: toddmilliken <milliktr@gmail.com>
IE stylesheets are added in addition to the global stylesheet. They shouldn’t need postcss transforms since they only support IE8 or less.
@toddmilliken
Copy link
Contributor Author

Added a new page to Framework wiki for configuring browser support: https://github.com/bu-ist/responsive-framework/wiki/Browser-Support

…starter into feature/autoprefixer

# Conflicts:
#	CHANGELOG.md
#	Gruntfile.js
#	ie.css.map
#	ie.min.css.map
#	languages/responsive-child-starter.pot
#	package-lock.json
#	package.json
#	style.css.map
#	style.min.css.map
@toddmilliken toddmilliken merged commit 355fa1a into develop Mar 4, 2019
@toddmilliken toddmilliken deleted the feature/autoprefixer branch March 4, 2019 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants