Comment 5 for bug 1809035
Revision history for this message
| Isaac Muse (facelessuser) wrote Re: Possibility of replace current select implementation? | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
This should close out the following issues. If for whatever reason the bugs still manifest, they can be referred to the Soup Sieve Issues page.
#1507608
#1664660
#1684968
#1692137
#1717850
#1717851
#1607476
I'm not really sure what this one is about: #1808797. If only one is wanted, I figure "select_one" can be used or "select(selector, limit=1)". And if limit == 1, a pattern such as "ol, ul" will not return 1 "ol" *and* one "ul", it will return either "ol" or "ul", whichever comes first. It can probably be closed right along with all the others. They can be redirected to Soup Sieve's Issues if they'd like to discuss it, but I have no plans of altering the behavior. They can implement their own "select" with Soup Sieve as I expose the 'match' command in the API which select is built on top of.