Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 24 16:11
    nerdkid93 closed #9
  • Aug 11 2020 09:46
    vinyll commented #208
  • Mar 20 2020 17:10
    AndrewBurdyug commented #208
  • Mar 20 2020 16:58
    lkraav commented #208
  • Mar 20 2020 08:55
    AndrewBurdyug opened #208
  • Mar 09 2020 20:58
    GearHead001 opened #207
  • Oct 10 2019 09:36
    janjelinek commented #206
  • Aug 20 2019 14:09
    asppsa closed #170
  • Jul 29 2019 15:19
    Janiczek edited #206
  • Jul 29 2019 15:19
    Janiczek opened #206
  • Jul 16 2019 09:42
    coderofsalvation opened #205
  • Mar 14 2019 20:30
    armartinez closed #8
  • Mar 10 2019 20:01

    csuwildcat on master

    update package version strings (compare)

  • Mar 10 2019 20:01

    csuwildcat on master

    update version and core repo li… (compare)

  • Mar 01 2019 07:23
    PioArchiver opened #204
  • Feb 28 2019 02:32
    PioArchiver commented #203
  • Feb 28 2019 02:32
    PioArchiver commented #203
  • Feb 28 2019 02:32
    PioArchiver opened #203
  • Feb 27 2019 00:48

    csuwildcat on 2.0.3-beta

    (compare)

  • Feb 27 2019 00:47

    csuwildcat on master

    Fix for custom even firing (compare)

KIP
@KipOmaha
3 HTML1415: Unexpected character: U+002D HYPHEN-MINUS (-)
examples2.html (41,15)

2 SCRIPT438: Object doesn't support property or method 'setPipeline'
elements.js (310,12)
Firefox console is below:
09:44:16.978 [Show/hide message details.] TypeError: this.xtag.data.thead.setPipeline is not a function[Learn More] elements.js:311:13
09:44:16.983 [Show/hide message details.] TypeError: this.xtag.data.tbody.setPipeline is not a function[Learn More] elements.js:328:13
Chong Kah Shiu
@kahshiu
Exactly. Its the custom tags own property, "this.xtag.data" object. I thought its an object available for use?
image.png
so I start sticking "this.xtag.data" with anything that I want to persist intrinsically within custom tag.
somehow, Chrome recognises it, but FF doesnt.
KIP
@KipOmaha
this.xtag = {}
you must set the xtag properties value to object
this.xtag = {}
this.xtag.data = {}
// than you add to the data object.
or maybe I misunderstood.
I'm not sure what is going on with Chrome, I will try the change I just suggested to see if I can get the last two errors to clear though.
KIP
@KipOmaha
For some reason the xtag HTMLElement prototype doesn't get attached to the DOM elements when its created during the lifecycle phase of the library in FF/Edge. I'm not sure if this a known issue, I don't maintain this library.
Maybe in FF/Edge the registration doesn't get complete for the create children element until the currently executing custom element is finished, so that the children your querying at the time really don't have the correct prototypes
KIP
@KipOmaha
yup I got it to find it using a setTimeout @kahshiu
KIP
@KipOmaha
Ok no I didn't sorry, but I did confirm that the tbody and thead at the time of the tables creation doesn't get the xtag element prototype.
KIP
@KipOmaha
Sorry :(
KIP
@KipOmaha
image.png
Above photo is of Firefox...I got it to work but I had to switch a couple things around.
Do you want to see a PR @kahshiu ?
Chong Kah Shiu
@kahshiu
Sorry, whats PR? Public Relations officer?
KIP
@KipOmaha
Oh sorry, I meant pull request. I can initiate a "PR" on your open repository you have your code in so you can see the code.
Chong Kah Shiu
@kahshiu
oh ok, please do.
Chong Kah Shiu
@kahshiu
btw, Ive found this following library to be a capable replacement for x-tags. I'll move my work to adopting it.
KIP
@KipOmaha
I'll send over the pull request today.
Also you may want to look at slimjs too.
KIP
@KipOmaha
Above is the link to the PR
@kahshiu
Raphael
@schnrap

Hi everyone,
I'm new to xtag, but can anyone tell me what the difference between the class notation and the object notation is? The documentation jumps between the two and I can't figure out, how these to stick together.
Thanks in advance for your time.

example:

// class notation
const Frank = xtag.create('x-frankenstein', class extends XTagElement {
  constructor (){
    alert("It's moving...it's alive!");
  }
});

// object notation 
xtag.create('x-clock', class extends XTagElement {
  connectedCallback () {
    this.start();
  }
  start (){
    this.update();
    this._interval = setInterval(() => this.update(), 1000);
  }
  stop (){
    this._interval = clearInterval(this._data.interval);
  }
  update (){
    this.textContent = new Date().toLocaleTimeString();
  }
  'tap::event' (){
    if (this._interval) this.stop();
    else this.start();
  }
});
KIP
@KipOmaha
The code you present both use ES6 classes, are you referring to the xtag.create and the xtag.register @schnrap ?
Raphael
@schnrap
My bad; I posted the wrong snippet.
The above examples use ES6 classes, while the documentation switches to plain objects when talking about pseudos.
xtag.register('x-foo', {
  content: '<input/>',
  events: {
    'tap:delegate(input)': function(){
      // Perform an action only when the user taps on an
      // <input/> element within your component.
    }
  }
});
Joao Oliveira
@joao-arvins
Hello. Anyone knows if v2 is compatible with IE? We are thinking of migrating from v1 to v2 but we need to support IE 11
KIP
@KipOmaha
@joao-arvins, last time I checked IE didn't support the es6 strings or much of es6 as far as I know. I believe that is one of the issues I ran into. Also the npm audits haven't been checking out. Do you have info on that?
KIP
@KipOmaha
if anyone is interested I have an update for v1.5.11 that I'm a not too far away from completing a customElements.define() conversion.
I was thinking of putting up a repo or making a PR.
I have it running currently just no jasmine or other tests, its just running on firefox without any customElements.js or any other poly
// It works almost the same.
xtag.register("my-elem", class() {
  constructor() {super();}
  static accessors() {
    return {
       myProp: { /* define getters and setters */ }
    }
    created() {}
    inserted() {}
    removed() {}
    attributeChanged() {}
  }
}
Above is an example
KIP
@KipOmaha
Check issues I will post the features that I get lined up.
KIP
@KipOmaha
The reason I change the register() method is for chrome...I want to use v2 but it comes back with npm audit problems. Since I'm not sure where to post npm audit problems I figured I try here.
could anyone give me guidance on that?
Bart van Leeuwen
@semanticfire
is there any sight on a v2 release ?
Bart van Leeuwen
@semanticfire
anyone ? :)
aolko
@aolko
if anyone is alive - is there an es5 version of v2?
i don't want to extend any classes
Allan Oloo
@OlooAllaN
Hello, everyone, does anyone know where I can get xtag v1 core.js?