Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Callbacks for Web Components #1446

Open
marschall opened this issue Oct 20, 2024 · 0 comments
Open

Callbacks for Web Components #1446

marschall opened this issue Oct 20, 2024 · 0 comments

Comments

@marschall
Copy link
Contributor

This is a brainstorming issue for further Web Components improvements aiming at better integration with other components and forms. First and foremost attributeChangedCallback() since attribute values are the interface a Web Component presents to the rest of the page. Here are some of the questions that we need to think about

  • observedAttributes must be static, how can we make this depending on the Seaside component class?
  • What should be interface for listening look like? An overridden method? A block?
  • How should a component be able to respond? Always a full component render?
  • Should we add an API to set attribute values on other components

Ideally this could then be further extended to support custom form elements using ElementInternals and checkValidity(), reportValidity(), setFormValue(), setValidity() methods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant