-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Custom elements as table rows break layout when importing resources as first business #668
Comments
@koenbeuk thanks for filing this issue. And sorry that somehow I missed it until now. The issue you encountered is because how Aurelia turns a template (or a html file content) into a view factory: it is first passed through native HTML5 parser via simple What can be done to avoid this is to make sure only TDs are children of <template>
<td>
<require from="..."></require>
</td>
</template> Can you try the aboe? |
Here is an example of it working: https://gist.run/?id=45a7d62b74673e35ed667412085baa7d |
@bigopon Thanks for the example, I already got it working that way :) |
@koenbeuk nice. I guess we can close this issue? |
It's not blocking me anymore, feel free to close if you deem best |
It seems we could really use some doc describing this scenario to help future folks. Would be great if you could help with this @koenbeuk ❤️ |
I'm submitting a bug report
1.10.1 and later (have not tested before)
Please tell us about your environment:
Operating System:
Windows 10
JSPM OR Webpack AND Version
webpack-cli 3.1.2
Browser:
Tested in Chrome
Language:
all
Current behavior:
When using
<tr as-element="custom-element">
inside a table, where the custom element starts by requiring other resources, the actual rendering is broken.Given
Gets rendered as:
Note how the td element is missing. When I remove the from custom-row.html- or when I place the inside the td element, things work as expected.
See: https://gist.run/?id=a5c449b7a1900f729cc36a97003c70bd
Expected/desired behavior:
In above example, I would have expected
The text was updated successfully, but these errors were encountered: