Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Repeater sub-controls and functions now acknowledge overall disabled state #1652

Conversation

kevinparkerson
Copy link
Contributor

Fixes #1534 by making sub-controls account for disabled state. The following items now don't work when the repeater is disabled:

  • view switching via the .repeater-views radio buttons
  • selecting items within repeater list
  • filtering items within repeater list
  • selecting items within repeater thumbnail

Additionally, I have fixed an issue where rendering a different view manually via the render method did not also change the selected view radio button :)

@swilliamset
Copy link
Contributor

Unit test please

@kevinparkerson
Copy link
Contributor Author

Dunno why the Travis build failed but:
I'm going to change the class checks to a "isDisabled" object check, plus add unit tests tomorrow morning :)

@@ -286,6 +286,8 @@

//row level actions click
this.$element.find('.table-actions tbody .action-item').on('click', function(e) {
if (self.$element.hasClass('disabled')) return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

set and use self.isDisabled instead of looking at class

BenjaminNeilDavis added a commit that referenced this pull request Dec 9, 2015
…bled

Repeater sub-controls and functions now acknowledge overall disabled state
@BenjaminNeilDavis BenjaminNeilDavis merged commit d9320b1 into ExactTarget:master Dec 9, 2015
@cmcculloh-kr cmcculloh-kr added this to the 3.13.1 milestone Nov 22, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

selectable repeater does not respect disabled state
4 participants