Skip to content

Release 9.9.6-alpha.3

Pre-release
Pre-release
Compare
Choose a tag to compare
@thet thet released this 16 Oct 10:55
· 173 commits to master since this release

9.9.6-alpha.3 (2023-10-16)

Features

  • core events: remove_event_listener - support removal by id and all at once. (2e78439)

    Previously registered events can now be removed by a matching id with no
    element given, like:
    remove_event_listener(undefined, "my-event-id");
    When called with no parameters like "remove_event_listener()" all
    registered events are removed.

  • core events: remove_event_listener - support wildcard ids. (b2d0651)

    The id parameter can be a wildcard string, e.g. test-*-event, which
    would match any event which starts with "test-" and ends with "-event".
    The wildcard "*" can be anywhere in the string and also be used multiple
    times. If no wildcard is present the search string is used for an exact
    match.

  • core utils: regexp_from_wildcard - Create regular expressions from wildcard strings. (4cf724a)

    This utility can be used for search strings with wildcards like "test-*-xyz".
    The wildcard can be at the beginning, somewhere in the middle or at the
    end and multiple wildcards can be used.
    This method was factored out from removeWildcardClass for broader usage.

Bug Fixes

  • core events: Fix references in add_event_listener and remove_event_listener. (7dd9aff)

    add_event_listener and remove_event_listener did incorrectly use an
    object instead of a map to store element references. This is now fixed.

  • core events: Fixes for remove_event_listener. (c2caf48)

    • Fix removing all events on a given element.
  • Clean up the event registry after removing events.
  • pat checklist: Fix incorrect usage of the dispatch method. (0e6eb01)

    This fixes a performance problem with pat-checklist.

  • pat-inject: Don't submit forms with invalid data. (a0fa4d2)

    Fix a problem with pat-inject and pat-validation where forms with
    invalid data could be submitted and the submit button wasn't inactive.
    The problem was fixed in two ways:

  • pat-inject now has a check for browser-native form validation. Invalid
    forms would not be submitted.

  • pat-inject now waits a tick before it get's initialized. Modern
    BasePattern based patterns including pat-validation are all deferred
    for 1 tick by design. pat-inject, being and older Pattern isn't
    deferred and thus initialized before pat-inject. It's initialized
    before pat-validation even though we have some Pattern initialization
    reorganization code in place - pat-inject not being deferred will have
    it's event handlers always run before any others. But now, with the
    1-tick defer in place, pat-inject's event handlers are run in the
    correct order - after pat-validation form validation which in case of
    an invalid form would also deactivate the submit button.

Maintenance

  • core utils: Dispatch - document postpone parameter. (cd7822c)

    Better document the postpone parameter of the dispatch method.

  • pat checklist: Infinite scrolling example. (18ac157)

    Add infinite scrolling example to demonstrate a performance problem
    which is solved by in this release.

  • pat checklist: Use Patternslib event factory. (e12aaac)

    Use Patternslib core event factory for the change event.

  • pat checklist: Use Patternslib event listeners. (69831f3)

    Change to Patternslib core event listeners to avoid double registration
    and allow better unregistration.

This fixes a performance problem with pat-checklist.