Skip to content

Releases: Nashorn/od-cocoon

v6.0.1

21 Jun 14:03
a426e12
Compare
Choose a tag to compare

Improvement to .subscribe/.fire event bus. Application base class now notifies off all previous events that took place instead of just last the way component instances work.

v6.0.0

14 Jun 22:59
Compare
Choose a tag to compare

Improvements to better declarative shadowDOM support in browser and electron and any browser not yet implementing DSD;
New publish/subscribe bus via this.subscribe("eventName") and this.fire("eventName")

v5.4.0

24 Feb 18:24
Compare
Choose a tag to compare
5.4.0

v5.3.0

12 Feb 12:37
Compare
Choose a tag to compare

Declarative ShadowDOM support; ShadowDOM deep queries via >>>

v5.2.2

12 Oct 18:42
Compare
Choose a tag to compare

v5.2.2

v5.2.1

10 Sep 14:18
Compare
Choose a tag to compare
component css is now parsed using template engine.

v5.2.0

15 Jul 11:52
Compare
Choose a tag to compare

Improvements to inheritance-based component skinning

v5.1.0

21 Apr 14:15
Compare
Choose a tag to compare

This version has support for themes. Components may now implement a getter theme() that returns the name of a theme:

Example:
namespace ui.components ( class Knob extends WebComponent { get theme(){ return "metal" } } )

This will force the component to use the theme named "metal" located at
src/ui/components/Knob/skins/metal/index.css

instead of the default index.css asset that is normally loaded.

Alternatively, the can be enforced globally in the HEAD tag using:
Config.THEME = "metal";

Components that inherit from a themed component will inherit the new theme
and will also attempt to load it's own theme named "metal", since the getter
is inherited. You may want to inherit the parents skin but not want to load
a them for the child, this can be overridden:

get theme(){ return null }

Which will load the sub-classed components default index.css.

v5.0.2

01 Apr 11:42
Compare
Choose a tag to compare

improved support for slots in shadowdom / lightdom; statemachine integrated for new Component2D;

v5.0.0

22 Jan 11:59
Compare
Choose a tag to compare

Breaking addEventListener change. New e.matchedTarget added to event signal. This new prop attached to the event object on callbacks will give you the real captured target that was clicked if it matches 4th argument of arc's overloaded addEventListener(). In previous versions of Arc/cocoon, e.target was attached to a pseudo event object via cherry picking of event props.

Now, the real event is handed back with a new 'matchedTarget' property. Example:

Given this HTML in your component:

<template>
  <button>
      <i class="fa fa-edit"></i>
  </button>
</template>

You may matched clicks at the button level, even if the real click occured deep in the icon:
addEventListener('click, e=> this.onDoSomething(e), false, 'button');

e.matchedTarget returns button as the intended target, not the icon inside the button that was clicked, which is e.target

onDoSomething(e) {
   alert(e.matchedTarget) 
}