Skip to content

Support both src attribute and source child element #126

Open
@mkeblx

Description

@mkeblx

Should model support setting a model resource via either a source child element(s) or a src attribute on the model element itself?

Currently the model explainer indicates that it should be via a source child element, and specifically via a src attribute as something that was considered but not chosen.

However, I noticed that in a recent cool presentation and associated materials for a model implementation that the src attribute was the primary method indicated for setting a model. I take this as a indication that there is strong interest in supporting src for one or more reasons (it's obviously visually cleaner and easier). It would be useful to discuss what we want model to support in this regard.


Explainer:

To change the loaded resource, the author should use existing DOM APIs to add, remove or modify children elements to the element
DOM API

with the section on options previously considered

Considered Alternatives
3. A simple src="" attribute instead of children

Metadata

Metadata

Assignees

No one assigned

    Labels

    agendaTo be discussed at a future CG meeting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions