[Issue 363] Weaver Components should use an alternate mechanism to display: none when components are ready.

TAMULib / weaver-components

Custom Web Components for the Weaver UI

MIT License

0 stars 1 forks source link

[Issue 363] Weaver Components should use an alternate mechanism to display: none when components are ready. #373

Closed kaladay closed 3 years ago

kaladay commented 3 years ago

On startup, weaver will remove all wvr-components-loading classes. The body element is reserved for last to ensure that the body doesn't become visible while other elements are being updated.

resolves #363