|
20 | 20 | Mixing in Enumerable has some unintended consequences; plus we want to improve the attributes API
|
21 | 21 |
|
22 | 22 | * Some ideas for a better attributes API?
|
23 |
| - * (closed) [#666](https://github.com/sparklemotion/nokogiri/issues/666) |
24 |
| - * [#765](https://github.com/sparklemotion/nokogiri/issues/765) |
| 23 | + * (closed) [#666](https://github.com/sparklemotion/nokogiri/issues/666) |
| 24 | + * [#765](https://github.com/sparklemotion/nokogiri/issues/765) |
25 | 25 |
|
26 | 26 |
|
27 | 27 | ## improve CSS query parsing
|
|
33 | 33 | chained :not pseudoselectors
|
34 | 34 |
|
35 | 35 | * better jQuery selector and CSS pseudo-selector support:
|
36 |
| - * [#621](https://github.com/sparklemotion/nokogiri/issues/621) |
37 |
| - * [#342](https://github.com/sparklemotion/nokogiri/issues/342) |
38 |
| - * [#628](https://github.com/sparklemotion/nokogiri/issues/628) |
39 |
| - * [#652](https://github.com/sparklemotion/nokogiri/issues/652) |
40 |
| - * [#688](https://github.com/sparklemotion/nokogiri/issues/688) |
| 36 | + * [#621](https://github.com/sparklemotion/nokogiri/issues/621) |
| 37 | + * [#342](https://github.com/sparklemotion/nokogiri/issues/342) |
| 38 | + * [#628](https://github.com/sparklemotion/nokogiri/issues/628) |
| 39 | + * [#652](https://github.com/sparklemotion/nokogiri/issues/652) |
| 40 | + * [#688](https://github.com/sparklemotion/nokogiri/issues/688) |
41 | 41 |
|
42 | 42 | * [#394](https://github.com/sparklemotion/nokogiri/issues/394)
|
43 | 43 | nth-of-type is wrong, and possibly other selectors as well
|
|
53 | 53 |
|
54 | 54 | * there are a few tickets about searches not working properly if you
|
55 | 55 | use or do not use the context node as part of the search.
|
56 |
| - - [#213](https://github.com/sparklemotion/nokogiri/issues/213) |
57 |
| - - [#370](https://github.com/sparklemotion/nokogiri/issues/370) |
58 |
| - - [#454](https://github.com/sparklemotion/nokogiri/issues/454) |
59 |
| - - [#572](https://github.com/sparklemotion/nokogiri/issues/572) |
| 56 | + - [#213](https://github.com/sparklemotion/nokogiri/issues/213) |
| 57 | + - [#370](https://github.com/sparklemotion/nokogiri/issues/370) |
| 58 | + - [#454](https://github.com/sparklemotion/nokogiri/issues/454) |
| 59 | + - [#572](https://github.com/sparklemotion/nokogiri/issues/572) |
60 | 60 | could we fix this by making DocumentFragment be a subclass of NodeSet?
|
61 | 61 |
|
62 | 62 |
|
|
68 | 68 | ## Better Syntax around Node#xpath and NodeSet#xpath
|
69 | 69 |
|
70 | 70 | * look at those methods, and use of Node#extract_params in Node#{css,search}
|
71 |
| - * we should standardize on a hash of options for these and other calls |
| 71 | + * we should standardize on a hash of options for these and other calls |
72 | 72 | * what should NodeSet#xpath return?
|
73 |
| - * [#656](https://github.com/sparklemotion/nokogiri/issues/656) |
| 73 | + * [#656](https://github.com/sparklemotion/nokogiri/issues/656) |
74 | 74 |
|
75 | 75 | ## Encoding
|
76 | 76 |
|
|
0 commit comments