Fixing explanations of onsuccess/onerror listeners for IndexedDB

[afonyaa]

Description

The paragraph that aimed to be fixed contained 2 issues:

1. Logical error: there is no 'success'/'error' events on DOM event type property, according to official specification https://html.spec.whatwg.org/multipage/indices.html#events-2

2. The explanation text was just hard to read and focus, so it is a bit simplified and more concised

Motivation

I made this change, so the developers do not be confused with unexpected 'error' / 'success' DOM event types

Additional details

https://html.spec.whatwg.org/multipage/indices.html#events-2

[github-actions]

Preview URLs

• /en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB

Flaws (2)

URL: /en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB
Title: Using IndexedDB
Flaw count: 2

• macros:
  • Macro produces link /en-US/docs/Web/API/IndexedDB_API/Basic_Concepts_Behind_IndexedDB which is a redirect
  • Macro produces link /en-US/docs/Web/API/IndexedDB_API/Browser_storage_limits_and_eviction_criteria which is a redirect

(comment last updated: 2025-06-24 15:06:51)

[wbamberg]

Description

The paragraph that aimed to be fixed contained 2 issues:

1. Logical error: there is no 'success'/'error' events on DOM event type property

The text doesn't say that though, it says that the success event is an Event whose type is "success", which is correct:

To fire a success event at a request, run these steps:

Let event be the result of creating an event using Event.

Set event’s type attribute to "success".

(from https://w3c.github.io/IndexedDB/#fire-success-event)

However I do agree that the existing text is confusing and wrong in other ways (specifically, there is no onsuccess() function: onsuccess is an attribute whose value is an anonymous function).