-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add support for web components #1419
Conversation
Interesting. I have not dabbled with Web Components yet... could you include an example on how this would be used? |
...ry/Seaside-Tests-Session.package/WAApplicationTest.class/instance/testPreFetchIsForbidden.st
Outdated
Show resolved
Hide resolved
Embedding Seaside components in a non-Seaside page without resorting to frames. <!DOCTYPE html>
<html>
<head>
<!-- -->
<script src="seaside-components.js" defer></script>
</head>
<body>
<!-- -->
<wa-component url="/examples/counter">Loading...</wa-component>
<!-- -->
</body>
</html> The components could be ajaxified so they could make use of full page refreshes without reloading the whole page. I'll work on a demo. |
Oh ok, I think I get it. The 'seaside-component.js' implementation uses the server-side to render the html contents? ps: see you tomorrow ;-) |
Yeah, exactly. I added some demo code in an additional commit. Still not sture what the ideal way to include custom scripts and styles is. |
- add support for template element - add support for slot element - add support for slot attribute
4b81c15
to
07d69e9
Compare
💜 |
This PR includes two changes:
Documentation: https://github.com/SeasideSt/Seaside/wiki/WebComponents
Fixes #1029