Skip to content

AudioBufferSourceOptions buffer seems like it could default to null #2668

Open

Description

@annevk

I didn't see a reason this needs to distinguish between null and missing? (Although the algorithms are a bit hard to follow.)

Activity

  1. annevk commented on Feb 8, 2026

    @annevk
    Author

    This also applies to ConvolverOptions it seems.

  2. added
    Needs DiscussionThe issue needs more discussion before it can be fixed.
    Agenda+Should be discussed at the next WG meeting. https://speced.github.io/spec-maintenance/about/
    on Feb 12, 2026
  3. padenot commented on Feb 17, 2026

    @padenot
    Member

    2026-02-17 call:

    What would be the impact of doing this vs. a default value? It's functionally equivalent in terms of Web Audio API.

    We're missing some language in the ConvolverNode case, it's not clear what happens when setting the .buffer to null when it wasn't null. In Firefox this clears internal state.

  4. annevk commented on Feb 17, 2026

    @annevk
    Author

    I'm not sure I understand the question. If they are indeed equivalent it's preferable to reduce the number of branches through IDL to reduce overall complexity.

  5. hoch commented on Apr 9, 2026

    @hoch
    Member

    Teleconference on Apr 9, 2026:

    • Update AudioBufferSourceOptions: Modify the Web IDL to set the default value of the buffer member to null.
    • Update ConvolverOptions: Align the buffer member in ConvolverOptions to also default to null.
    • Define ConvolverNode.buffer Nullification: Add explicit language to the specification detailing what happens when ConvolverNode.buffer is set to null after it has already been assigned a value (e.g., ensuring it correctly clears the internal state/impulse response).
  6. added
    category: enhancementSubstantive changes that do not add new features. https://www.w3.org/policies/process/#class-3
    on Apr 20, 2026
  7. added
    Needs EditsDecision has been made, the issue can be fixed. https://speced.github.io/spec-maintenance/about/
    and removed
    Needs DiscussionThe issue needs more discussion before it can be fixed.
    Agenda+Should be discussed at the next WG meeting. https://speced.github.io/spec-maintenance/about/
    on Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs EditsDecision has been made, the issue can be fixed. https://speced.github.io/spec-maintenance/about/category: enhancementSubstantive changes that do not add new features. https://www.w3.org/policies/process/#class-3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions