Skip to content

web components? #23

@uniqname

Description

@uniqname

Is not the logic extension of this Web Components? WCs allow the author to create semantic tags with semantic attributes any or all of which can obviously be targeted by CSS selectors. Does AM provide additional value above and beyond more semantically specific elements and attributes or is this an interim solution? Is there a use case where AM and WC live side-by-side?

BTW, same logic applies to BEM and the many other conventions for attaching style hooks to markup, which may actually answer my "interim" question. It does beg whether spending the time to develop a formal spec for AM is wise if it's going to be relatively short lived due to upcoming implementations of existing web specs.

Just wondering what the roadmap for this may be given the foreseeable future?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions