this again?

[Polymorphe57]

A subtility with this:

Click on "Update 2" brings an error "Uncaught RangeError: Maximum call stack size exceeded"

see in playground

[ged-odoo]

linked to #1317

[sdegueldre]

Behaves as expected: unqualified names are looked up on the context meaning that calling functions directly inside of templates (instead of calling them as a method on this) causes them to be bound to the rendering context, causing the code to be essentially equivalent to

const renderingContext = {
  update() {
    return this.update();
  }
}

In general, it's advisable to never call functions using their unqualified names in templates as they will be implicitly bound to the rendering context:

<div t-on-click="() => method()"/> <!-- incorrect -->
<div t-on-click="() => this.method()"/> <!-- correct -->
<div t-on-click="() => props.method()"/> <!-- correct -->
<div t-on-click="() => this.props.method()"/> <!-- correct but needlessly qualified: the method will be bound to props in both cases -->

Hopefully this can help people who stumble upon this issue in the future. We will address this issue in owl 3 (for which we have no timeline as of yet)