Change Details

The toast module creates a new object of itself while initializing. It takes only some ms, but isn't really needed most of the time. Maybe we should revisit that (I think it's mostyl done to render a pending toast, e.g. after an edit was saved) and separate the pending toast rendering from the toast itself, so it's only rendered, if really neded. It also creates an empty toast element in the DOM (which is normal while rendering): {F654276} {F654282}

The toast module creates a new object of itself while initializing. It takes only some ms (2,7ms), but isn't really needed most of the time. Maybe we should revisit that (I think it's mostyl done to render a pending toast, e.g. after an edit was saved) and separate the pending toast rendering from the toast itself, so it's only rendered, if really neded. It also creates an empty toast element in the DOM (which is normal while rendering): {F654276} {F654282}

The toast module creates a new object of itself while initializing. It takes only some ms (2,7ms), but isn't really needed most of the time. Maybe we should revisit that (I think it's mostyl done to render a pending toast, e.g. after an edit was saved) and separate the pending toast rendering from the toast itself, so it's only rendered, if really neded. It also creates an empty toast element in the DOM (which is normal while rendering): {F654276} {F654282}