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
Replace --skip-aggressive-merging
with all property merges implemented.
#290
Labels
Milestone
Comments
GoalSmashers
pushed a commit
that referenced
this issue
Jun 8, 2014
Using `--skip-aggressive-merging` / `noAggressiveMerging` switch skips property merging based on order. Will be fixed in #290.
GoalSmashers
pushed a commit
that referenced
this issue
Jun 8, 2014
Using `--skip-aggressive-merging` / `noAggressiveMerging` switch skips property merging based on order. Will be fixed in #290.
jakubpawlowicz
changed the title
Replace 2.2
Replace 2.2 Apr 18, 2015
--skip-aggressive-merging
with all properties merges implemented.--skip-aggressive-merging
with all property merges implemented.
jakubpawlowicz
added a commit
that referenced
this issue
May 4, 2015
Adds compatibility switches for `ch`, `vh`, `vm`, `vmax`, `vmin`, and `vw` units. Note we need #290 to fully support all use cases. Currently it'll be just for implemented shorthands.
jakubpawlowicz
changed the title
Replace 2.2
Replace Aug 19, 2015
--skip-aggressive-merging
with all property merges implemented.--skip-aggressive-merging
with all property merges implemented.
This was referenced Sep 16, 2015
jakubpawlowicz
added a commit
that referenced
this issue
Jan 1, 2017
jakubpawlowicz
added a commit
that referenced
this issue
Jan 1, 2017
Why: * Another step to move away from aggressive merging.
This was referenced Jan 4, 2017
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * It's a shorthand property, so not straightforward to implement in shorthand/override compacting; * pending in #860.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * It's a shorthand property, so not straightforward to implement in shorthand/override compacting; * pending in #861.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * It's a shorthand property, so not straightforward to implement in shorthand/override compacting; * pending in #254.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * Border is a complex case where both `border` and all its components: `border-color`, `border-style`, and `border-width` are components. Also `border-(bottom|left|right|top)` are shorthands too. * this commit restores aggressive merging shorthand overriding right inside shorthand compacting code.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * Aggressive merging was replaced by override merging; * it supports much more properties now so aggressive merging won't be missed; * it also overrides based on understandability not merely a position in output file. Side notes: * This is a safe change as if a property is not configured to be overridable it won't be; * overhauls `canOverride` functionality to prevent features like vendor prefixes or variables from overriding widely supported values; * overhauls validating values by allowing known values, which strictly doesn't make it a full validator but rather a way of telling if a value *may* be valid.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * Internet Explorer `filter` / `-ms-filter` are unsupported since IE 10, which is also clean-css new default compatibility; * can be restored by using `ie7`, `ie8`, or `ie9` compatibility modes.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
jakubpawlowicz
added a commit
that referenced
this issue
Jan 18, 2017
Why: * All those optimizations are dealing with properties so the new name better reflects its role; Also: * renames `overrideCompactor` to `overrideProperties`; * renames `compactorOptimize` to `optimizeProperties`. * cleans up property optimizing code calling from level 2 optimizations due to removal of aggressive merging, see #290.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 19, 2017
Why: * Aggressive merging was replaced by override merging; * it supports much more properties now so aggressive merging won't be missed; * it also overrides based on understandability not merely a position in output file. Side notes: * This is a safe change as if a property is not configured to be overridable it won't be; * overhauls `canOverride` functionality to prevent features like vendor prefixes or variables from overriding widely supported values; * overhauls validating values by allowing known values, which strictly doesn't make it a full validator but rather a way of telling if a value *may* be valid.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 19, 2017
Why: * Internet Explorer `filter` / `-ms-filter` are unsupported since IE 10, which is also clean-css new default compatibility; * can be restored by using `ie7`, `ie8`, or `ie9` compatibility modes.
jakubpawlowicz
added a commit
that referenced
this issue
Jan 19, 2017
Why: * All those optimizations are dealing with properties so the new name better reflects its role; Also: * renames `overrideCompactor` to `overrideProperties`; * renames `compactorOptimize` to `optimizeProperties`. * cleans up property optimizing code calling from level 2 optimizations due to removal of aggressive merging, see #290.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: