Closed petronbot closed 8 years ago
@petronbot Want me to review this? At a glance this looks so awesome. :)
@klepas Yes please, I've just done a rebase to fix conflicts so this now incorporates the latest from develop.
LGTM. Looks reallllly good.
I think we should devote some time to revisit the documentation setup after this refactor. What do you think @petronbot and @joolswood?
For sure @klepas It'll be a substantial job.
Specifically with the IE templates, as this affects so many components, wondering whether we would document in it's own top level section, or include a reference within a part of every page, for example the 'Accessibility & browser support' accordion/section.
A11y and browser support are related, but I want to keep them separate from hereon in.
How verbose were you thinking of going with the IE conditional documentation? I think most of this could be done as commented sections within the code directly, imho.
I think I need to sit down and walk through it with you @klepas
As discussed with @klepas have logged a content debt ticket (DESIGN-431) for the restructured SCSS folder. Working on MVP text for the IE mixin.
LGTM.
@klepas I've tested the conditional styles as working in IE6-8, do you think that's sufficient to tick off cross browser/device testing? And do you think this needs any design review?
[…] do you think that's sufficient to tick off cross browser/device testing?
Yup, considering it’s for IE.
And do you think this needs any design review?
Do we have anything specific to ask Gary to test out of this?
Merge conflicts resolved and Changelog updated, will merge when build is finished.
Description
This PR includes some changes to the CSS to make it possible to target specific versions of IE with styles directly in the SCSS:
There are 3 new stylesheets generated in the build, one each for IE6, 7 & 8. They can be included using conditional comments:
I've also restructured the SCSS folder to make dependencies more clear between partials:
Definition of Done
npm test
)