1.3 is due out ... when it's done. We're hoping early spring. On Thu, Dec 17, 2009 at 7:53 PM, Jon <[email protected]> wrote:
> Thanks! Can't wait, is that some time in the near future? > > On Dec 17, 4:14 pm, Aaron Newton <[email protected]> wrote: > > I don't really recommend it, but if this is mission critical to you (i.e. > > you can't wait until 1.3) you could, in theory, drop in another selector > > engine. > > > > 2009/12/17 Fábio M. Costa <[email protected]> > > > > > Its fixed for the new version of mootools (1.3). It will include a new > > > Selector engine calle Slick, that is totally awzme. > > > > > -- > > > Fábio Miranda Costa > > > Solucione Sistemas > > > Engenheiro de interfaces > > > > > On Thu, Dec 17, 2009 at 9:16 PM, Jon <[email protected]> wrote: > > > > >> I'm trying to write an attribute selector with commas in it but it > > >> seems to match everything or at least not what I'm looking for when I > > >> add a comma. When I try my selector in CSS, it hits the right things > > >> but in Mootools it doesn't work. > > > > >> Example: p[something^="This,Color,"] > > > > >> I've gotten in touch with one of the people who helped write the w3c > > >> spec and there shouldn't be an issue with having a comma and if there > > >> was it should be able to be escaped by a \. > > > > >> Anybody else had this issue? Mootools developers can you help? > > > > >> Thanks! >
