Results 1 to 3 of 3

Thread: ComboBox and BoundList pageSize inconsistency

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTJS-8188 in 4.2.
  1. #1
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Saint-Petersburg, Russia

    Default ComboBox and BoundList pageSize inconsistency


    Ext version tested:
    • Ext 4.2.0 beta

    • The pageSize config option of ComboBox and BoundList confuses a bit. The name of the config option assumes that it can be used to manage page size, but according to the sources it is actually used as a boolean to show or not a PagingToolbar (also it is used in the ComboBox's doQuery, but again as a boolean). And the page size is actually managed by the Store's pageSize. Yes, it works because JavaScript interprets 0 as false, and not 0 as true. But I am talking about the inconsistency.
    • I assume this thing just stays since ExtJS 3 where the ComboBox's pageSize is really used as a number. But maybe is it time to change? Maybe a boolean config like "enablePaging" or "showPagingToolbar" would be better. Or are you planning to pass the ComboBox's pageSize to its Store's pageSize?
    • Actually, it is reported in the docs, but it doesn't look just a doc issue.

    Frameworks and Tools for .NET Developers
    Ext.NET - Ext JS for ASP.NET - Examples | Twitter
    Bridge.NET - Write C#. Run JavaScript! - Live | Twitter

  2. #2
    Sencha Premium User evant's Avatar
    Join Date
    Apr 2007
    Sydney, Australia


    Yes, the pageSize config is essentially just a boolean now because paging is handled by the store itself. It's mostly a backwards compatibility thing, but we should probably phase out the config for something a bit clearer.
    Twitter - @evantrimboli
    Former Sencha framework engineer, available for consulting.
    As of 2017-09-22 I am not employed by Sencha, all subsequent posts are my own and do not represent Sencha in any way.

  3. #3
    Sencha User SimoAmi's Avatar
    Join Date
    Oct 2008
    New York


    It makes sense to at least mark the property as deprecated, or document the new behavior just like in the PagingToolbar documentation.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts