search

w3c / miniapp-lifecycle

MiniApp Lifecycle
https://w3c.github.io/miniapp-lifecycle/
Other
7 stars 6 forks source link

Application Error event in the explainer #1

Closed xfq closed 3 years ago

xfq commented 4 years ago

In the lifecycle explainer, the "Lifecycle States defined by existing W3C specs" is "N/A".

I wonder if we can use the error event on Element/Window?

espinr commented 4 years ago

I wonder if we can use the error event on Element/Window?

I think it's the most appropriate correspondence. A window error is thrown when a user agent failed to load a resource or it cannot be interpreted (this includes script execution errors).

QingAn commented 3 years ago

In the lifecycle explainer, the "Lifecycle States defined by existing W3C specs" is "N/A".

I wonder if we can use the error event on Element/Window?

I edited the explainer and created a pull request. But I am wondering that since MiniApp's runtime is different with web runtime, is it necessary to use the error event on Element/Window?

xfq commented 3 years ago

I don't quite understand what "use the error event" means here. According to my understanding, we are looking for a mapping to existing Web specifications, rather than directly using this event.

xfq commented 3 years ago

Link to PR: https://github.com/w3c/miniapp-lifecycle/pull/6

QingAn commented 3 years ago

I don't quite understand what "use the error event" means here. According to my understanding, we are looking for a mapping to existing Web specifications, rather than directly using this event.

Then I made a mistaken assumption. I think we can agree that the goal is to make the mapping happen. So, back to the explainer, can we agree on the PR: #6?