1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Crass Change History
====================
1.0.6 (2020-01-12)
------------------
* Number values are now limited to a maximum of `Float::MAX` and a minimum of
negative `Float::MAX`. (#11)
* Added project metadata to the gemspec. (#9 - @orien)
1.0.5 (2019-10-15)
------------------
* Removed test files from the gem. (#8 - @t-richards)
1.0.4 (2018-04-08)
------------------
* Fixed whitespace warnings. (#7 - @yahonda)
1.0.3 (2017-11-13)
------------------
* Added support for frozen string literals. (#3 - @flavorjones)
1.0.2 (2015-04-17)
------------------
* Fixed: An at-rule immediately followed by a `{}` simple block would have the
block (and subsequent tokens until a semicolon) incorrectly appended to its
prelude. This was super dumb and made me very sad.
1.0.1 (2014-11-16)
------------------
* Fixed: Modifications made to the block of an `:at_rule` node in a parse tree
weren't reflected when that node was stringified. This was a regression
introduced in 1.0.0.
1.0.0 (2014-11-16)
------------------
* Many parsing and tokenization tweaks to bring us into full compliance with the
[14 November 2014 editor's draft][css-syntax-draft] of the CSS syntax spec.
The most significant outwardly visible change is that quoted URLs like
`url("foo")` are now returned as `:function` tokens and not `:url` tokens due
to a change in the tokenization spec.
* Teensy tiny speed and memory usage improvements that you almost certainly
won't notice.
* Fixed: A semicolon following a `@charset` rule would be omitted during
serialization.
* Fixed: A multibyte char at the beginning of an id token could trigger an
encoding error because `StringScanner#peek` is a jerkface.
[css-syntax-draft]:http://dev.w3.org/csswg/css-syntax-3/
0.2.1 (2014-07-22)
------------------
* Fixed: Error when the last property of a rule has no value and no terminating
semicolon. [#2][]
[#2]:https://github.com/rgrove/crass/issues/2
0.2.0 (2013-10-10)
------------------
* Added a `:children` field to `:property` nodes. It's an array containing all
the nodes that make up the property's value.
* Fixed: Incorrect value was given for `:property` nodes whose values contained
functions.
* Fixed: When parsing the value of an at-rule's block as a list of rules, a
selector containing a function (such as `#foo:not(.bar)`) would cause that
property and the rest of the token stream to be discarded.
0.1.0 (2013-10-04)
------------------
* Tokenization is a little over 50% faster.
* Added tons of unit tests.
* Added `Crass.parse_properties` and `Crass::Parser.parse_properties`, which can
be used to parse the contents of an HTML element's `style` attribute.
* Added `Crass::Parser.parse_rules`, which can be used to parse the contents of
an `:at_rule` block like `@media` that may contain style rules.
* Fixed: `Crass::Parser#consume_at_rule` and `#consume_qualified_rule` didn't
properly handle already-parsed `:simple_block` nodes in the input, which
occurs when parsing rules in the value of an `:at_rule` block.
* Fixed: On `:property` nodes, `:important` is now set to `true` when the
property is followed by an "!important" declaration.
* Fixed: "!important" is no longer included in the value of a `:property` node.
* Fixed: A variety of tokenization bugs uncovered by tests.
* Fixed: Added a workaround for a possible spec bug when an `:at_keyword` is
encountered while consuming declarations.
0.0.2 (2013-09-30)
------------------
* Fixed: `:at_rule` nodes now have a `:name` key.
0.0.1 (2013-09-27)
------------------
* Initial release.
|
