v4.4.0

• Add support for a disable-if attribute, similar to show-if but for disabling items.
• Fixes for <tangy-input> so that if disabled and required it does not block proceeing on a form.
• Error logging functionality designed for editor use was blocking errors from the Javascript Console, this is now fixed.

v4.3.9

Add the property "value" when the row marker is clicked for each of the buttons - csv reports
- PR: #103

v4.3.8

• fix auto-stop to enable revealing of hidden radio buttons when a correction is made.
  • Issue: Tangerine-Community/Tangerine#1519
  • PR: #102

v4.3.6

• Fixed auto-stop for radio buttons bug bug. Limit hideInputsUponThreshhold to tangy-radio-buttons inputs. No longer need to call hideInputsUponThreshhold in on-change event when using incorrect-threshold in tangy-radio-buttons.
• Issue: Tangerine-Community/Tangerine#1519
• PR: #100

v4.3.3

• Vertical center for tangy-toggle-button contents / tangy-timed items. c677ffb
• Fixes for saving and resuming <tangy-checkboxes-dynamic>. #98

v4.3.0

• Features
  • Improvements and support on all inputs for error-text, hint-text, question-number, and content translations.
    • Issue: Tangerine-Community/Tangerine#1655
    • PR: #88, #86
  • Add support to <tangy-qr> for scanning data matrix codes.
    • Issue: Tangerine-Community/Tangerine#1653
    • PR: #87
  • New "Capture Item at N Seconds" feature for <tangy-timed> will prompt Data Collector to mark which item the child last read after a specific amount of time.
    • Issue: Tangerine-Community/Tangerine#1586
    • PR: #95
  • New goTo('itemID') helper function to navigate users to a specific item given some item level on-change logic.
    • Issue: Tangerine-Community/Tangerine#1652
    • PR: #92
  • New <tangy-signature> input for capturing signatures.
    • Issue: Tangerine-Community/Tangerine#1656
    • PR: #90
  • Visibility of labels and/or icons on item navigation now configurable with <tangy-form-item hide-nav-icons> and <tangy-form-item hide-nav-labels>.
    • Issue: Tangerine-Community/Tangerine#1682
    • PR: #73
• Fixes
  • Fix performance issues caused by needless TangyForm.on-change events from firing when they don't need to.
    • Issue: Tangerine-Community/Tangerine#1656
    • PR: #89
  • Fix data collector reviews completed fullscreen form
    • Issue: Tangerine-Community/Tangerine#1629
    • PR: #75
  • <tangy-eftouch auto-progress> now distinguishes between going next on the time limit and going next on a number of selections. The API is now <tangy-eftouch go-next-on-selection=2> for going next on 2 selection and <tangy-eftouch go-next-on-time-limit> for going next on the time limit.
    • Issue: Tangerine-Community/Tangerine#1597
    • PR: #84
  • <tangy-eftouch> content is now more likely to fit above the fold, not overlap with content above it, be more consistent on smaller screens, and also adapt to screen size changes.
    • Issue: Tangerine-Community/Tangerine#1591, Tangerine-Community/Tangerine#1587
    • PR: #79
  • <tangy-eftouch> suffered from going to next item twice due to time limit and selection being made at in a close window. This is now fixed.
    • Issue: Tangerine-Community/Tangerine#1596
    • PR: #76
  • Fix Partial Date validation and for disabled attribute not reflecting
    • Issue: Tangerine-Community/Tangerine#1683
    • PR: #71

v4.2.0

Added the exit-clicks attribute to tangy-form and tangy-form-item, which is for the number of times a user must click the exit fullscreen button before that mode is deactivated.

v4.1.1

Fix tangy-select test regression and work on EFTouch transition sound plays only on auto-progress #137

v4.0.0

• Enable content of a form to be styled from the parent document. #64

Upgrade instructions:
This is considered to be a major release because some users' forms would look into a form item's contents using tangyFormItemEl.shadowRoot.querySelector(...). The contents of the form can now be accessed at tangyFormItemEl.querySelector(...). If you have any use of shadowRoot in our form content, beware. The advantage of moving this content out of the shadow DOM is that you can now style it directly from your app.

v3.23.0

• Add ability to reference inputs.NAME in valid-if attributes. #65