Results 1 to 6 of 6

Thread: Binding to multiselect combobox.selection has a bug?

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium User
    Join Date
    Sep 2011
    Location
    Tamworth, NSW, Australia
    Posts
    1,353

    Default Binding to multiselect combobox.selection has a bug?

    If a bind the disabled property of a button to a multiselect combo.selection property, it doesn't work the first time if only one record is selected. If I select a record, the button should be enabled, but I have to select two then one again for it to behave like it should. It is only the first time it doesn't work properly.

    Here is a fiddle demonstrating the problem.

  2. #2
    Sencha - Support Team bjdurham85's Avatar
    Join Date
    Mar 2014
    Posts
    962

    Default

    Hi Marc,

    Thanks for the info. While I can see the scenario you've described using the multiselect on a comboBox has been deprecated and should instead be replaced with a Ext.form.field.Tag or Ext.view.MultiSelector

    Do these produce the desired affect?

    Bryan

  3. #3
    Sencha Premium User
    Join Date
    Sep 2011
    Location
    Tamworth, NSW, Australia
    Posts
    1,353

    Default

    I haven't tried either of those in this use case yet, and was not aware of the combobox multiselect deprecation. That is very sad news indeed because the more items I select in a tagfield the bigger it gets and my efforts so far to restrict its size have got nowhere. I'd like users to be able to select lots of things without the tagfield taking up loads of space :-(

    Edit: I've just noticed "grow: false" (but it has no effect), so "growMax: 25" seems to do the job sufficiently for now.

  4. #4
    Sencha Premium User
    Join Date
    Sep 2011
    Location
    Tamworth, NSW, Australia
    Posts
    1,353

    Default

    Also, if you set a width on a tagfield you get very strange results. It seems to want a whole heap of extra blank space in there or else it'll show an internal scroll bar. These tagfields do not make very good substitutes for a good old-fashioned multiselect combobox. I've updated the Fiddle to a tagfield now. So, either way, I'm going to have to waste a lot of extra screen real estate for these things :-(

  5. #5
    Sencha Premium User
    Join Date
    Sep 2011
    Location
    Tamworth, NSW, Australia
    Posts
    1,353

    Default

    Tag fields are not as good as combo boxes as far as accessibility is concerned (using NVDA screen reader) so I'm going to have to stick with comboboxes for the time being. I hope Sencha improves the accessibility of tagfields before ultimately stripping comboboxes of their multiselect capability.

  6. #6
    Sencha Premium User
    Join Date
    Mar 2015
    Posts
    40

    Default

    Quote Originally Posted by bjdurham85 View Post
    While I can see the scenario you've described using the multiselect on a comboBox has been deprecated and should instead be replaced with a Ext.form.field.Tag or Ext.view.MultiSelector

    Do these produce the desired affect?

    Bryan
    Yes they are, please see the https://fiddle.sencha.com/#fiddle/20sh

Similar Threads

  1. [OPEN] ComboBox Selection Binding Bug in 5.1
    By davs416 in forum Ext 5: Bugs
    Replies: 3
    Last Post: 17 Oct 2016, 1:06 PM
  2. Replies: 5
    Last Post: 17 Nov 2014, 7:04 AM

Tags for this Thread

Posting Permissions

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