Closed marschall closed 4 months ago
Attention: Patch coverage is 23.93617%
with 143 lines
in your changes missing coverage. Please review.
Project coverage is 49.10%. Comparing base (
1378e9e
) to head (07d69e9
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Interesting. I have not dabbled with Web Components yet... could you include an example on how this would be used?
Interesting. I have not dabbled with Web Components yet... could you include an example on how this would be used?
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 ;-)
The 'seaside-component.js' implementation uses the server-side to render the html contents?
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.
💜
This PR includes two changes:
Documentation: https://github.com/SeasideSt/Seaside/wiki/WebComponents
Fixes #1029