Loading...

Search jQuery

Search

jQuery Forum

Screen name:
Shikyo

Shikyo's Profile

4 Posts

39 Responses

0 Followers

Activity Trend

Last 30 days

Loading Chart...

Show:

Expanded view
List view

How to deal with page flickering?

[5 Replies]
- 21-Jan-2013 11:11 AM
- Forum: Using jQuery UI
jQuery ui widgets require a minimum amount of html to be instantiated. When instantiating, the widget's create method is called which should render the full html and add any required classes.

The recommended place to instantiate widgets is in the document ready handler. This is causing me some issues because in old (slow) browsers or just slow pc's the user can see the page changing (flickering).

In the past i've always been able to overcome this problem by simply rendering the full html, including all the css classes. But now in jquery ui 1.10 this is no longer working for all widgets. Currently trying to do this with the accordion widget and the cornering breaks when i pre render the html.

Putting the instantiation right below the html is not always an option either because some widgets do positional calculations in the create method which gets corrupted if the page has not been loaded completely.

Apparently the jquery ui team and the ui mobile team for that matter don't seem to recognize this problem. I don't really understand why that is because it makes for a less smooth user experience.

How to deal with page flickering?

Unbinding events for 1.8 plugins in 1.9

[0 Replies]
- 22-Nov-2012 08:29 AM
- Forum: Developing jQuery UI
In widget factory 1.8 i used to bind event like this:

this.element.on("click." + this.widgetName, $.proxy(this._doStuff, this));

Which got automatically unbound when calling the destroy method.

Now in widget factory 1.9 there is a eventNamespace variable which seems to be the widgetName + some number.

this._on($element, { click: this._doStuff });

Is essentially the same as:

this.element.on("click." + this.eventNamespace, $.proxy(this._doStuff, this));

In the destroy method jQuery UI1.9 event are unbound like this:

this.element.unbind( this.eventNamespace ) ;

Which results in 1.8 plugins not properly getting destroyed.

To clarify, when i bind an event handler the 'old' way, $element.on("click.myPlugin", $.proxy(this._doStuff, this));
The new widget factory will unbind like this.element.unbind("myPlugin1") ;

Passing elements through options

[4 Replies]
- 11-Jul-2012 04:21 AM
- Forum: Developing jQuery Plugins
Dear all,

I have several custom plugin that can have elements passed into the options. As per convention these elements can be either a selector, dom element or jQuery object.

In order to make that convention fly i create jQuery objects for all elements passed through options.

For example:
1. (function($)
2. {
3. "use strict";
5. $.widget("ui.somePlugin",
6. {
7. // Default options
8. options:
9. {
10. someElement: null,
11. },
12. _create: function()
13. {
14. // Convert to jQuery object
15. this.options.someElement = $(this.options.someElement);
16. }
17. });
18. })(jQuery);
But i'am not sure this is the best approach because the options the user passes in get changed.

Also because it's converted to a jQuery object the user can pass in multiple elements and sometimes this gives an undesired effect.

So my question is; how to go about passing elements though options in a custom plugin? Is it ok to convert those options to jQuery objects and how to deal with users passing multiple elements when you only want one element?

unbinding a document ready handler

[1 Reply]
- 12-Jul-2011 07:12 AM
- Forum: Using jQuery
Hello all,

We are using the unobtrusive validation library that using the standard jquery validation plugin.
This extension adds a handler to document ready which parses the document for validation meta data.
2. $(function () {
3. $jQval.unobtrusive.parse(document);
4. });
For our application this behavior it not wanted so i ended up commenting out the code shown above. But i don't want to modify standard libraries because that bring in complications when upgrading to a newer version.

What i want to do is unbind the last bound document ready handler after the unobtrusive libary loads.

Is there a way to unbind the handler in the code shown above?

«Prev
Next »