Not sure which browsers you are targeting or the selectors you require, but
querySelector might be an alternative without requiring the extra library.
http://caniuse.com/#feat=queryselector
On 1 Jan 2013 05:14, Sebastián Gurin sebastigu...@gmail.com wrote:
Thank you Thomas for the clarification
On Tuesday, January 1, 2013 6:13:32 AM UTC+1, Sebastián Gurin wrote:
Thank you Thomas for the clarification and for taking a look to the
project. Didn't know about the new xsiframe. I'm reading some documentation
and fixing my projects.
about wrapper/port thing, I thought a wrapper was
Yes, I know, sizzle will use querySelector when available and it has an
implementation for old browsers. Regards
On Tuesday, January 1, 2013 8:24:51 AM UTC-2, Chris Price wrote:
Not sure which browsers you are targeting or the selectors you require,
but querySelector might be an alternative
Oh another term :( I think I will call it wrapper as you suggested before.
I like the first level wrapper vs second level wrapper idea for
discriminate between them. Thank you again for all the help!
--
You received this message because you are subscribed to the Google Groups
Google Web
I needed a lightweight solution for CSS selectors in
com.google.gwt.dom.client.Element so I made a GWT port of the JavaScript
library *sizzle*js.com/ http://sizzlejs.com/
GWTSIZZLE : http://code.google.com/p/gwtsizzle/
Since it has a very simple JavaScript API it only took me 1 hour to author
On Monday, December 31, 2012 10:55:50 PM UTC+1, Sebastián Gurin wrote:
I needed a lightweight solution for CSS selectors in
com.google.gwt.dom.client.Element so I made a GWT port of the JavaScript
library *sizzle*js.com/ http://sizzlejs.com/
Ah, this is not a port, it's a wrapper.
Also
Thank you Thomas for the clarification and for taking a look to the
project. Didn't know about the new xsiframe. I'm reading some documentation
and fixing my projects.
about wrapper/port thing, I thought a wrapper was when you put the JSO as a
pure java class attribute. Then you delegate all
