Dave Cardwell wrote:
Actually thinking again, delete from var public = { right down to (and
including) $.browser = public;, and after the var private = {}
block, add $.browser = private;. That should work better.
Note that public and private are reserved names in javascript. Most
Thanks for the heads up - I'll sort that this weekend too.
Best wishes,
Dave Cardwell ~ http://davecardwell.co.uk/
Jan Sorgalla wrote:
Dave Cardwell wrote:
Actually thinking again, delete from var public = { right down to (and
including) $.browser = public;, and after the var private = {}
I recently noticed that a new version of jQBrowser was available and I like
the new features but it appears to be breaking jQuery all over the place
when I try and use it with jQuery Rev 249. It also conflicts with Interface
as it uses some checks for MS IE. Basically it make Interface think that
Hi Aaron.
I've received a few emails from people asking to change back to using
$.browser.msie, and as such the 1.0 release will do so. In the meantime
I'd recommend either switching back to 0.1, or the following change to
the source *should* work (untested):
Switch the line:
$.browser =
Hi,
Has anyone else had this problem? I would imagine it has to do with the
change of object properties ($.browser.msie) to methods ($.browser.msie()).
pretty shure.
@dave: I don't understand why you whant to use functions anyway here.
I suggest you simply use your private object as public
Actually thinking again, delete from var public = { right down to (and
including) $.browser = public;, and after the var private = {}
block, add $.browser = private;. That should work better.
Best wishes,
Dave Cardwell ~ http://davecardwell.co.uk/
Dave Cardwell wrote:
Hi Aaron.
I've
I use a public interface to prevent direct access to what should be
private state inside the object. Upon recent reflection, with
JavaScript the added complexity probably just isn't worth it, so I will
be modifying the plugin to suit in the near future.
Best wishes,
Dave Cardwell ~
